You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd appreciate your thoughts on pulling Bank Transactions.
End date
One good reason for not pulling BTs is they can disappear - a Xero user could do a Bank Statement reconciliation and then later undo it, and redo it. This could result in hanging Contributions in CiviCRM with no corresponding BTs in Xero.
My assumption, though, is that after a period of time a BT would become static and no further changes would occur (with rare exceptions). Let's say that period is 2 business days after the BT is last modified (eg, assume that a BT created on Day 1 can be replaced on Day 1 or Day 2 but not Day 3).
The pull for BTs could work like that for Invoices except with an extra parameter 'end_date'. The parameters for the job would be something like ...
plugin=xero
start_date=midnight 5 days ago
end_date=midnight 3 days ago
... and the job would pick up BTs modified at least 5 days ago, but not in the last 3 days ('midnight 3 days ago' covers the case where a BT created on Friday morning might be replaced any time up to Monday afternoon).
Corollary - having both Bank Transactions and Invoices in the civicrm_accounts_invoice table
It seems Bank Transactions and Invoices might run into each other here. Would setting ...
connector_id=1
... help?
The text was updated successfully, but these errors were encountered:
I'll take a read of this & mull it in a bit - but one quick question - are you using bank transactions or just invoices? (most of our customers just do invoices but a recent one wanted bank transactions so it's pretty new)
We use Invoices if the transaction originates in CiviCRM (eg, credit card payment, online contribution using the 'pay later' option.) We use Bank Transactions for transactions that don't (eg, regular EFT payment) so we can take advantage of Xero's Bank Statement matching rules.
In lieu of a BT pull, our proposal is to export BTs from Xero as a report, import them into CiviCRM, and set a custom field "Suppress Xero Invoice" to "Yes". Our Invoice push hook prevents Contributions with that field set from being pushed to Xero.
Eileen,
I'd appreciate your thoughts on pulling Bank Transactions.
End date
One good reason for not pulling BTs is they can disappear - a Xero user could do a Bank Statement reconciliation and then later undo it, and redo it. This could result in hanging Contributions in CiviCRM with no corresponding BTs in Xero.
My assumption, though, is that after a period of time a BT would become static and no further changes would occur (with rare exceptions). Let's say that period is 2 business days after the BT is last modified (eg, assume that a BT created on Day 1 can be replaced on Day 1 or Day 2 but not Day 3).
The pull for BTs could work like that for Invoices except with an extra parameter 'end_date'. The parameters for the job would be something like ...
... and the job would pick up BTs modified at least 5 days ago, but not in the last 3 days ('midnight 3 days ago' covers the case where a BT created on Friday morning might be replaced any time up to Monday afternoon).
Corollary - having both Bank Transactions and Invoices in the civicrm_accounts_invoice table
It seems Bank Transactions and Invoices might run into each other here. Would setting ...
... help?
The text was updated successfully, but these errors were encountered: