Share
Report
13Hi community,
I'm building an outbound AP e-invoicing integration and need a trigger that fires once for every posted vendor invoice, so I can create a staging record for a batch to transmit. It has to catch all of them: PO-based, non-PO (pending vendor invoice), and potentially AP invoice journal entries.
Options so far:
- CoC on a posting class: (PurchInvoiceJournalPost): Only covers the PO path, and I can't be sure I've enumerated every creator (an ISV may be involved on the non-PO side this is TBD).
- DataEventHandler on VendInvoiceJour.OnInserted: Agnostic since every path converges there, but it runs inside the posting transaction and also fires for data migration.
- Recurring reconciliation batch: Iterate over VendInvoiceJour for new records, no posting or ISV dependency, relies on a cut-off date.
From my internal testing so far, I believe I have verified that each of these mechanisms being PO invoice, pending vendor invoice and vendor invoice journal does create a VendInvoiceJour > VendInvoiceTrans record which will be the data pickup point for the integration
For anyone who's built statutory e-invoicing integration, did you hook the table, the posting classes, or reconcile afterwards? Which held up over platform updates and with ISVs in the mix?
Thanks in advance.
All responses (
Answers (
