Taxes

Taxes calculates the tax due at checkout, records it as a committed sale after the buyer pays, and - when you turn on reporting - files, remits, and issues any mandated e-invoice. You keep your own checkout and PSP - Outpost is not a payment orchestrator.

Calculation and reporting are two separate switches. Calculation stands alone. Reporting is optional. Tax liability moves to Outpost only when both are on - the combination Outpost calls Tax of Record. Outpost does not take liability for tax it does not control.

The flow

The shape is the same everywhere. You quote tax, charge on your own PSP, commit the sale once payment succeeds, and - when reporting is on - Outpost files and issues any mandated e-invoice asynchronously.

Who remits

Calculation onlyYou remitOutpost quotes tax at checkout and records the committed sale. You file and remit to the authorities yourself. Liability stays with you.

Tax of RecordOutpost remitsTurn on reporting and Outpost files, remits, and issues any mandated e-invoice such as Brazil NFS-e. Liability for the tax it controls moves to Outpost.

Either way you call the Tax API at checkout, so the wiring is the same - see Integration.

What you get

A calculation returns a single aggregate taxAmount to add to the charge - a per-component breakdown is not on the public API today. When Outpost remits on your behalf, that tax is netted out of your Payments proceeds, so you reconcile it in Settlement. Whether Outpost files and remits at all, and what it costs, is set by your contract.

Coverage varies by country and tax type - Brazil NFS-e is live today. For what is supported where and the setup for your region, talk to Solutions.

API surface

You work with three objects - a tax calculation quoted at checkout, the committed tax transaction, and catalogue products you import for classification. Full schemas live in the API reference.

Endpoints

Webhook events

EVENTe_invoice.issued