Separating the tax filing from the sale itself

Alternatives considered

Discarded

Keep the external communication inside the sale operation.

Chosen

Confirm the sale first and send the fiscal submission afterward.

Decision made

Confirm the sale before running the communication with the tax authority. Fiscal numbering and duplicate protection stay inside the transactional operation, while the external submission happens after the sale is confirmed.

Rationale

Keeps sale transactions short and avoids holding a lock while waiting on an external communication.

Frequently asked questions

What did Pymerce decide about "separating the tax filing from the sale itself"?

Confirm the sale before running the communication with the tax authority. Fiscal numbering and duplicate protection stay inside the transactional operation, while the external submission happens after the sale is confirmed.

Does confirming a sale count as issuing a fiscal invoice?

Not in Pymerce — they're two separate steps. The sale is confirmed first, with its fiscal numbering and duplicate protection already resolved inside that same transaction; sending it to the tax authority happens afterward, as a separate step.

What happens if the e-invoicing service is down at the moment of the sale?

The sale doesn't sit there waiting on that response, because the fiscal communication runs after it's already confirmed. That way, an outage on an external service can't block closing a sale that's already settled on the business side.

Can the fiscal numbering get lost if the submission to the tax authority fails?

The fiscal numbering and duplicate protection are generated and kept inside the sale's own transaction, before the external submission ever happens. The submission can be retried later without putting that data at risk.