Transferring Custom Data
JustOn Billing & Invoice Management can transfer information that is beyond the scope of the default data model from your source records to invoices and bookkeeping data:
- Transferring data to invoices
- To copy specific information from source records to subscriptions (with the automatic subscription build) or invoices (with the invoice run), you use the ON Field Mechanism. The feature is based on custom fields whose API names start with
ON_
– if there is a field with a matching API name on the target object, JustOn copies the field value. - Transferring data to bookkeeping data
- To copy specific information from invoices or invoice line items to booking details and, from there, to accounting documents or accounting document items, you just need custom fields with the same API name and data type, without specific prefixes.
Explicitly set fields
JustOn sets the following fields explicitly when creating booking details according to the applied business logic. This is why they will not be copied as additional custom fields:
Booking Detail Target Field | Source Object and Field |
---|---|
Account | Invoice.Account |
AccountName | Invoice.AccountName |
AccountNo | InvoiceLineItem.GLAccount CollectiveAccount.Account |
AccountRule | AssignmentRulesGLAccount.Name CollectiveAccount.Name |
Amount | InvoiceLineItem.PosTotalNet InvoiceLineItem.PosTotalTax |
BIC | Invoice.BankCode |
Balance | Balance.Name |
BankAccountOwner | Invoice.BankAccountOwner |
BillingCity | Invoice.BillingCity |
BillingPractice | Item.BillingPractice |
BookingDate | Invoice.Date Invoice.ON_BookingDate |
BookingPeriod | dynamically set on creation |
BpAccountNo | Invoice.DebtorNo Account.ON_DebtorNo CollectiveAccount.BpAccount |
Center | InvoiceLineItem.Center |
CostObject | InvoiceLineItem.CostObject |
CurrencyIsoCode | Invoice.CurrencyIsoCode |
CustomerCity | |
CustomerName | |
Exported | dynamically set on creation |
IBAN | Invoice.BankAccount |
InvoiceNo | Invoice.Name |
Invoice | Invoice.Id |
Name | dynamically set on creation |
PaymentDate | Balance.Date |
Region | Invoice.Region |
Subscription | Subscription.Name |
TaxCode | InvoiceLineItem.TaxCode |
TaxRate | InvoiceLineItem.TaxRate |
Type | dynamically set on creation |
VATId | Account.TaxNumber |
As an example, assume the following use case:
You produce invoices from subscriptions that are built on top of opportunities, and you transfer bookkeeping data to DATEV. Now your DATEV instance requires the field
buCode
. You want this information already set on the opportunity – that is, your source record – and from there, transferred to the subscription, the invoice, the booking detail and the accounting document item.
To this end, you create
- the custom ON field
ON_BuCode__c
on the Opportunity object, - the custom ON field
ON_BuCode__c
on the Subscription object, - the custom field
BuCode__c
on the Invoice object, and - the custom field
BuCode__c
on the Booking Detail object.
The Accounting Document Item object already includes the required target field BuCode__c
.
Once set up, JustOn will copy the given value
- from
ON_BuCode__c
on the opportunity toON_BuCode__c
on the subscription when building the subscription, - from
ON_BuCode__c
on the subscription toBuCode__c
on the invoice when creating the invoice (via the invoice run), - from
BuCode__c
on the invoice toBuCode__c
on the booking detail when generating the bookkeeping data (on invoice finalization), - from
BuCode__c
on the booking detail toBuCode__c
on the accounting document item when transferring accounting documents to DATEV.
Related information:
Understanding the ON Field Mechanism
Enabling Additional Information on Booking Details
Additional Accounting Document Fields