Delta Pre-Invoice Generation
The New Delta Pre-Invoice Generation feature ensures that your invoicing process is accurate and up-to-date by comparing the latest invoiced amounts with new amounts and creating delta pre-invoice items for any differences. This feature handles various aspects of invoicing, including timesheet activities, flexible payment plans, packages, and invoice contacts, making your invoicing more efficient and reliable
How it works
When delta invoicing is activated, the generation of pre-invoices is based on comparing the latest invoiced amounts with the new amounts, which include the changes. When you generate a new pre-invoice, the system will fetch the latest invoiced items and compare them with the new campaign amounts to identify any differences. The system will create delta pre-invoice items for any differences found between the latest invoiced amounts and the new amounts.
Delta pre-invoices are generated and invoice items are created when the delta optimization version is activated or after the Delta Preinvoice generation when the campaign item is adjusted.
The delta changes are made in the pre-invoice of their respective period or, if the period is closed for invoicing, the adjustments are made in the next open period.
How to call Delta Preinvoice generation
Legal Entities are now mapped with Delta pre-invoice generation
When the delta invoicing is enabled on the Admin settings the new delta pre-invoice generation is called during the following processes:
New PreInvoice generation button on the Media Campaign
Pre-Invoice wizard (Lightening)
Scheduled Pre-Invoice Batch Job
the global invocable method that calls the batch job →
GenerateInvoiceBatch.doGenerateInvoice(can be called from everywhere, custom apex code and flows)The end campaign item feature for items based on actuals (triggered by the media campaign trigger)
The end campaign item feature for items based on linear distribution (triggered by the end campaign item feature)
The
FlowInvocableProcessfor flow executions (“CreateInvoicesBatchJob")The optimizer activation triggered Process Builder flow →
ProcessCompleteEventOptimizingVersion.flow- this action can be disabled since PreInvoice generation is triggered with optimizing version activationInvoice Wizard (Lightening) - The pre-invoice update stage is included
Invoice Wizard (To be deprecated) - The pre-invoice update stage is included
Financial Changes
Only financial changes are considered by the pre-invoice generation and the following items are compared to evaluate if it is a financial change or not.
Invoice Item Amount Comparison:
comparison of invoice item amounts already invoiced with those that would be calculated by the next pre-invoice generation, for each specified payment interval (total, yearly, half-yearly, quarterly, monthly, weekly).
This comparison is done at the invoice item level, considering amounts B3, B2, B1, N1, N2, and N3
Invoicing Based on Linear Distribution vs. Actual Delivery
There are two types of invoicing: based on the linear distribution and based on actual delivery data (utilizing actual delivery from Revenue Schedules).
For linear distribution, amounts are calculated based on the runtime of the campaign item across payment intervals.
For actual delivery, amounts are calculated based on delivery data in the Revenue Schedule, for billing categories such as CPM, CPC, vCPM, CPCV, and Budget
Weekly payment interval is using Revenue Schedules Daily and has to be enabled through the admin settings
New Delta Pre-Invoice generation will delete and not create any 0 amount pre-invoice items when the campaign items are fully invoiced. This is also relevant for already invoiced campaign items, where only the runtime is switched.
New Invoice and invoice item fields
A new invoice item fields have been created to improve the handling of the Delta Invoicing:
Delta Change Reason
API Name: DeltaChangeReason__c
During the optimization, the reason for the change for every single Campaign item can be added and it is mapped to the invoice item to use it in the Invoice PDF to show the reason for the change.
Referenced Invoice Number
API Name: ReferencedInvoiceNumber__c
This field stores the original invoice number which was adjusted and will be shown on the Invoice PDF as a reference.
Position Reference
API Name: PositionReference__c
This is a reference to the previous version of the invoice item related to this campaign item
Invoice Item Creation Type
API Name: CreationType__c.
A new picklist field has been created to identify an invoice item creation type. This field is preset automatically and should not be changed by the user.
Following are the picklist values:
None - This creation type is the same as the related invoice. Nothing will change when it comes to displaying this item
Flexible Payment Plan - Invoice items created based on the Flexible Payment Plan
Technical Reversal - This is the negative clone of the previous version
Delta Adjustment - This is a new version of the Invoice item after the change. This item would display the new Delta fields
Cancelation - This is a new version of the Invoice item after the cancelation.
The Cancelation creation type is a new picklist value on this field. It should be added to the Invoice item object after installation
The following new fields for delta invoicing are created which will calculate the outstanding amount based on changes done for Campaigns and what was already invoiced.
Invoice API Name | Invoice Field Label | Invoice Item API Name + Logic |
|---|---|---|
| Outstanding Gross Amount B3 |
Additional Condition: |
| Outstanding Gross Amount B2 |
Additional Condition: |
| Outstanding Gross Amount B1 |
Additional Condition: |
| Outstanding Invoiced Amount N1 |
Additional Condition: |
| Outstanding Invoiced Amount N2 |
Additional Condition: |
| Outstanding Invoiced Amount N3 |
Additional Condition: |
| Outstanding Non-Media Amount |
Additional Condition: |
| Outstanding DST Amount |
Additional Condition: |
| Outstanding Nontaxable Amount (DST) | Based on
|
| Outstanding Taxable Amount (DST) | Based on
|
| Outstanding VAT Amount (Type 1 (A)) |
|
| Outstanding VAT Amount (Type 1 (B)) |
|
| Outstanding VAT Amount (Type 2 (A)) |
|
| Outstanding VAT Amount (Type 2 (B)) |
|
| Outstanding Taxable Amount (VAT Type 1) |
|
| Outstanding Taxable Amount (VAT Type 2) |
|
| Outstanding Nontaxable Amount (VAT Total) | Based on
|
QR code feature users should map the correct amount to the ESR reference.
The following invoice fields will calculate the outstanding + the already paid amount:
Invoice Field API Name | Invoice Field Label | Invoice Item API Name + Logic |
|---|---|---|
| Gross Amount B3 |
Additional Condition: |
| Gross Amount B2 |
Additional Condition: |
| Gross Amount B1 |
Additional Condition: |
| Invoiced Amount N1 |
Additional Condition: |
| Invoiced Amount N2 |
Additional Condition: |
| Invoiced Amount N3 |
Additional Condition: |
| Non-Media Amount |
Additional Condition: |
| DST Amount |
Additional Condition: |
| Nontaxable Amount (DST) | Based on
|
| Taxable Amount (DST) | Based on
|
| VAT Amount (Type 1 (A)) |
|
| VAT Amount (Type 1 (B)) |
|
| VAT Amount (Type 2 (A)) |
|
| VAT Amount (Type 2 (B)) |
|
| Taxable Amount (VAT Type 1) | Based on
|
| Taxable Amount (VAT Type 2) | Based on
|
| Nontaxable Amount (VAT Total) | Based on
|
The general amount calculation is described here: https://advendio.atlassian.net/wiki/spaces/SO/pages/128161786
Following Invoice Formula fields are created for Delta.
Formula | Delta API Name |
|---|---|
|
|
|
|
|
|
Following Invoice Formula fields are not created for Delta, however, they can be created as custom fields if needed.
Formula | Delta API Name | Delta Label | Normal Formula API Name (can be taken as reference) |
|---|---|---|---|
|
| Outstanding Invoiced Amount Gross (DST) |
|
|
| Outstanding VAT Total (Type 1) |
|
|
| Outstanding VAT Total (Type 2) |
|
|
| Outstanding Taxable Amount (VAT Total) |
|
|
| Outstanding VAT Total |
|
|
| Outstanding Invoiced Amount Gross (Total) |
|
|
| Outstanding Early Payment Discount abs. |
|
|
| Outstanding Invoiced Amount Gross (incl. EPD) |
|
Assigning Accounting Periods
Each legal entity has associated accounting periods, typically structured on a monthly basis. In the updated feature, accounting periods play a crucial role in assigning and calculating invoice dates for pre-invoices.
The Delta Pre-Invoice Generation process ensures that all pre-invoices have an assigned accounting period. If the invoice date matches an open accounting period, that period will be assigned to the pre-invoice. If no matching accounting period is found, the system will search for the next open accounting period.
Supposing accounting periods are not yet created when the pre-invoices are generated. In that case, the accounting period field will remain empty and will be updated during the next pre-invoice generation once the accounting periods are created.
If there is an open accounting period before the latest closed accounting period (ordered by until date), we will ignore those open accounting periods. No accounting period will be assigned to related pre invoices until new period is open after the latest closed.
Example: Open matching accounting period in the past, with NO gap between latest closed and earliest next open
Campaign Item runs in June 2024
Accounting Period July 2024 is closed but Accounting Period June 2024 is still open (somehow)
The next (open) Accounting Period is in August 2024
Start Delta Pre-Invoice Generation
-> Pre-Invoice with Accounting Period August 2024 assigned will be createdIf there is a gap between the latest closed accounting period and the next open accounting period, no invoice item related to a closed accounting period will be assigned.
Pre-Invoice Items that match a certain open Accounting Period in the future will still be assigned to that Accounting Period, even if gaps in between Accounting Periods exist.
“Invoice Merging Exception”
When the accounting periods are already there and the current accounting period is closed the invoice items of the current month will merge into the pre-invoice of the next open period as a separate line item. This is true for all cases except, when the payment of the Media Campaign is due at the “end of the interval” the invoice items of the closed month do not get merge into the pre-invoice of the next open period instead it generates two separate invoice in the same period.
In order to close the accounting period all Pre-invoice within this accounting period should be invoiced or deleted, otherwise the validation will throw an error.
Change Accounting Period of created Pre-Invoice to September 2024 (keep Invoice Date July 1st)
Close Accounting Period July 2024
Run Delta Pre-Invoice Generation
-> pre-invoice Invoice Date changed to August 1st and Accounting Period did not change (September 2024)!
-> pre-invoice item related to CI #1 was update (LastModifiedDate)Example 2: Invoice Date (Manual) of Pre-Invoice was set to a future month
Create Campaign Item #1
Runtime July
Run Delta Pre-Invoice Generation
-> one pre-invoice and one pre-invoice item got created
-> pre-invoice with Invoice Date July 1st and Accounting Period July 2024 was created
-> pre-invoice item related to CI #1 was created
Set Invoice Date (Manual) of created Pre-Invoice to August 10th
-> Invoice Date changed to August 10th
Run Delta Pre-Invoice Generation
-> pre-invoice was update (LastModifiedDate), Invoice Date (August 10th) and Accounting Period (July 2024) did not change!
-> pre-invoice item related to CI #1 was update (LastModifiedDate)Example 3: Invoice Date of Pre-Invoice was changed manually or by some process
Create Campaign Item #1
Runtime July
Run Delta Pre-Invoice Generation
-> one pre-invoice and one pre-invoice item got created
-> pre-invoice with Invoice Date July 1st and Accounting Period July 2024 was created
-> pre-invoice item related to CI #1 was created
Change Invoice Date of created Pre-Invoice to July 15th
Run Delta Pre-Invoice Generation
-> pre-invoice Invoice Date was updated (back) to (July 1st) and Accounting Period (July 2024) did not change!
-> pre-invoice item related to CI #1 was update (LastModifiedDate)
Important the payment start
after Billingperiodwill be treated asbefore / during Billingperiodfor the invoice date calculation for case where the initial matching accounting period is closed, this makes sure that the pre-invoice items related to the past get quicker invoiced rather than waiting for a later date only because theafter Billingperiodin combination with the dates from the earliest open accounting period from the future. See the example below:
Have following accounting periods created for the following cases:
July 2024 (closed)
August 2024 (closed)
September 2024 (closed)
October 2024 (open)
All Media Campaigns are set up with…
Payment Interval: "monthly"Payment Start: "after Billingperiod"Payment Due To: "due to beginning of interval"
Create Campaign Item #1
Runtime July -> September
Run Delta Pre-Invoice Generation
-> pre-invoice #1 is created with Invoice Date 1st October and Accounting Period October 2024
-> pre-invoice item related to CI #1 July created
-> pre-invoice item related to CI #1 August created
-> pre-invoice item related to CI #1 September createdSetting the Invoice date
The invoice date for a pre-invoice is calculated using three key fields: payment interval, payment due, and payment start. The system then checks if this invoice date matches the start and end dates of the relevant accounting period.
Invoice date will always be consistent with the assigned accounting period. If there is no matching accounting period, the Invoice Date will be always the first day of the next open accounting period.