Wokflow clarification

chatry

We would like to ensure we fully understand the complete workflow of an invoice, from creation to final delivery and acknowledgment. Please clarify the following points:

Invoice Workflow

After a taxpayer registers and prepares an invoice in their ERP, should the following API calls be executed in order?

Generate IRN

Generate QR Code

Validate invoice

Sign invoice

Transmit invoice

Is this correct?

Sign and Transmit Behavior

Does Sign Invoice send the invoice to FIRS, or only produce a signed document?

Does Transmit Invoice send the invoice to FIRS, to the recipient, or both?

If the recipient Access Point Provider is offline, does /transmit queue the invoice or fail immediately?

** Confirm Endpoint**

For /confirm/{IRN}, what exactly do the fields transmitted and delivered represent, and when do they become true?

Our confusion arises because it is unclear whether Sign Invoice already triggers a transmission to FIRS, and whether /confirm will update transmitted value to "true", meaning teh /sign invoice will automatically update the trasmitted value field in the /confirm endpoint to "true", and same doubts arises for delivered value when it will become "true".

Payment Status

As the issuer of the invoice, we should update the payment status before executing /report for fiscalization purposes once the invoice is “paid”?

Is partial payment allowed, and if so, how should it be declared?

Lookup Endpoint

What is the purpose of the Lookup endpoint, and when should it be executed in the workflow?

Receiver Workflow

As a recipient of the invoice, is configuring a webhook and calling the download endpoint sufficient?

Are there any additional actions the receiver must perform?

Thank you in advance

SysAdmin

Dear @chatry,

This has already been explained in detail here:

E-Invoice Lifecycle/Flow & APP API Usage Questions https://community.firsmbs.com/d/58-e-invoice-lifecycleflow-app-api-usage-questions
Clarification on B2B E-Invoicing Flow & Status Messages https://community.firsmbs.com/d/133-clarification-on-b2b-e-invoicing-flow-status-messages/2

You may also find additional perspectives on this topic in other related threads within the community.

Kindly let me know if you still have any further questions or require additional clarification.

chatry

Hello,
Thank you for your answers.

I’m still not sure about two things:

As a taxpayer using an accredited APP to send invoices, is it mandatory to share the API key and API secret with them, or is the cryptographic keys text file alone sufficient?

For the B2C flow, based on which field in the schema can we determine whether the invoice is intended for a B2B or B2C flow?

Thank you,

SysAdmin

Dear @chatry,

The specific credentials to be shared depend entirely on your APP’s implementation architecture.

However, typically, your APP does not require your API Key and Secret. Instead, only the cryptographic key should be shared, and this should be with your System Integrator (SI), not the Access Point Provider (APP), except in a scenario where the APP is performing both roles.

chatry

Hello,

Please, can you answer the second part of my question: “For the B2C flow, based on which field in the schema can we determine whether the invoice is intended for a B2B or B2C flow?”

I’m not sure if we can rely solely on whether the invoice includes the AccountingCustomerParty field. In some B2B cases, the client might forget to generate the AccountingCustomerParty, and in that situation, the invoice could be incorrectly considered as B2C.

Thank you in advance

SysAdmin

chatry Accounting Customer Party is compulsory for B2B but optional for B2C.