Approved invoices post to Xero as bills

One bill per approved invoice, and its attachment. The supplier is resolved to a Xero contact, every line carries its own account code and its own tax, tracking categories are applied where you use them, and the PDF the vendor emailed is attached to the bill where the invoice arrived with one. A multi-line invoice maps line by line rather than as a single lump, and the tax on the lines adds up to the tax on the bill to the cent. It writes nothing else: it does not edit a bill that already exists, and it never pays anything.

Yes. Connect both and an approved invoice posts to each connected ledger, as one bill in each, under a single export run. Each ledger is tried on its own, so one refusing does not roll the other back. When that happens the document reads partially exported rather than posted, names the ledger that took it, and offers a retry for the one that did not. Retries are idempotent in both, so retrying cannot create a second bill.

No. inletAP is not Xero certified and is not listed on the Xero App Store. Certification requires a number of live customer connections we do not have yet, so it is ahead of us rather than behind us, and we would rather say that here than let you find out in the marketplace search box. The connector itself works today — you connect it from inside inletAP.

No, and we are not going to call it one. Bills go one way: inletAP posts them into Xero. The only thing that comes back is the nightly reconciliation check, which starts on the Starter plan: it reads the bills we posted and records what your ledger actually holds, so a bill that was changed or deleted in Xero shows up as a difference rather than as a silent disagreement. Nothing in Xero is edited or overwritten by that check, and on the free plan nothing reads your ledger at all.

No. Xero puts tracking on each line, so one Xero bill can carry a different property on every line. The ceiling is that a Xero organization defines at most two tracking categories in total, so properties have to be one of the two you already use. There is no Xero equivalent of coding a line to a unit as a sub-customer — that one stays QuickBooks-only, and we are not going to imply otherwise.

The batch records the reason in the words Xero used — an account code that is not on the chart, a supplier with no contact mapped, a tax rate that does not exist in that organization — and offers a retry. A refusal never posts a partial bill: the bill either exists in Xero in full or it does not exist at all. Where a document could not be coded safely, inletAP holds it back rather than posting a supplier short.