Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invoice already paid by a third party or the buyer #41

Open
svanteschubert opened this issue Oct 24, 2023 · 1 comment
Open

Invoice already paid by a third party or the buyer #41

svanteschubert opened this issue Oct 24, 2023 · 1 comment

Comments

@svanteschubert
Copy link
Owner

svanteschubert commented Oct 24, 2023

Background

Invoice already paid by a third party or the buyer known at the time of invoicing

French Use Case n°2: invoice already paid by buyer or third party designated for invoicing at time of invoice issue

For this management case, two sub-cases are to be considered:

  1. Invoice already paid by buyer
  2. Invoice already paid by a third party (adding an actor to the process)

The specific features of the data and associated management rules are :

  1. Billing frame "Deposit of a previously paid invoice".
  2. Due date equals payment date
  3. Amount paid (BT-113) equal to total invoice amount
  4. Amount payable (BT-115) equal to 0
  5. In sub-case 2, the third party who has already paid the invoice must be entered in the PAYER (EXT-FR-FE-BG-02). The supplier receives the invoice statuses, so that he can indicate whether the invoice has been collected and update the "collected" status transmitted to the public invoicing portal.

image

Figure 1: Invoice already paid by buyer or third party designated for invoicing

NOTE: The image numbering of the ver2.2 image was here manually fixed according to the one given by ver2.3

The specific features of the life cycle or associated processes are :

  1. Transmission of flow 1 by the supplier
  2. The fact that the invoice has already been paid does not exempt the supplier from transmitting the e-reporting of payment data ("cashed" status) when the transaction falls into the category of services.
  3. The "cashed" status can be sent at the same time as the invoice is issued

NOTE:
The text/pictures of this use case no. 2 were taken from the French government site!
The text was extracted from V2.3 - deepl English DOCX and any pictures were taken from V2.2 - original English PDF)

@edmundgray
Copy link
Collaborator

edmundgray commented Nov 6, 2023

Paid amount (BT-113) is set to the amount paid in advance and Bt-115 (Amount due for payment) is set to zero or the remaining balance if not fully paid.

related issues are #54, #49, #56, #53, #42, #43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants