Received documents
Documents sent to your taxpayers — read through the same feed as everything you send.
Documents sent to your taxpayers arrive automatically, with no separate inbox to poll. They show up as
direction: "inbound" rows in the same feed as everything a taxpayer sends:
- List transactions with
direction=inbound(orstatus=received) to page through them, or leave both off to see them merged with outbound traffic in one feed - Get a transaction by id for one row's full delivery and tax-report detail
- Download a document for the transmitted UBL itself, or a rendered PDF
- Webhooks to be notified the moment one lands, via
document.received, rather than polling for it
An inbound row's transaction_id works everywhere an outbound one does — the three endpoints above
don't distinguish direction in how you call them, only in what comes back (delivery: null, no
events, status fixed at received; see Status values).
No parsed line-item breakdown
The API surfaces the fields every transaction carries — parties, totals, delivery and tax-report state — but not a parsed breakdown of an inbound document's lines, addresses, or payment terms. Download the XML and read it directly for that detail; it's the exact bytes the sender transmitted, so nothing about it can drift from a parsed copy.