Skip to main content
Every tax invoice has a sending side and a receiving side. Mixing up the two parties means the invoice is issued to the wrong business, so it helps to align on the terms before you make a call.

​
The two parties

Supplier-Key is the key of the sending side (supplier), not the receiving side.Supplier-Key takes the supplierKey of the supplier itself that issues the tax invoice. The receiving side (supplied party) information goes in the supplied field of the request body. Swapping the two values issues the invoice to a different business than intended.

​
Who is the supplier?

The Bolta API is typically used in a model where a platform issues tax invoices on behalf of its own members - as with delegated issuance or reverse issuance. In this model, the entity that actually issues the tax invoice is the supplier. The platform first registers the supplier via the Register Supplier API, then issues invoices by putting the returned supplierKey into the Supplier-Key header.

​
Different from “customer” in the web service

The “customer” referred to in the [Customer Management] menu of the Bolta web service is the counterparty - that is, the supplied party that receives the tax invoice. By contrast, the supplier identified by the key in the API is the side that sends the tax invoice. The parties they point to are opposite, so take care when using the web service and the API together.

​
Cash receipt terms

The cash receipt API uses the following terms. As with tax invoices, Supplier-Key identifies the issuer.
For cash receipts, set Supplier-Key to the issuer’s key. Enter the receiving party’s information in recipient.