Supplier intercompany invoices
The supplier BP invoice entry function is used to manage the supplier invoicing process outside of the typical sales cycle.
This function cannot be used to manage the order or the receipt note for the stock receipt (etc.). When issuing the invoice, the data required for accounting is recorded.
As for customer tracking (open item statements, payment management, etc.), the process is similarly carried out for invoices that come from the complete cycle or that come simply from the entry of a BP invoice.
- In this document, the term 'invoice' has a generic meaning: it can be an invoice, a credit note, a debit note or a credit memo.
- Invoices generated from recurring invoices cannot be deleted if the invoices are used as the reference template (first/original recurrence).
Additionally, the invoice should not be modified if it is also used as the reference invoice.
For Swiss legislation: Refer to the Swiss localization how to guide for detailed information on setting up and using ISR (Inpayment Slip with Reference) or QR-bills.
Specificities linked to supplier intercompany invoices
- This function is available only if the INTCO - Intercompany transactions activity code is active.
- Invoices can be generated only if the selected company has INTCPYINV - Intercompany invoices (TRS chapter, INV group) set to "Yes".
If the company is set up for intercompany invoices, a reference to a target company, site, and the dimensions for each line can be entered.
If the target company does not match the source company, the general ledger accounts associated with the target company will be used along with the target company dimensions.
The following occurs if the target company entered on the line is not equal to the source company:
- The first account column is linked to the COA of the target company main general ledger.
- For the subsequent COA columns, an entry is made only if there is a COA for this ledger type in the accounting core model of the target company. If not, then the column will be skipped.
- Only the dimension type codes associated with the displayed/entered ledgers can be entered. If the ledger is not displayed, then the dimensions for the target company cannot be entered.
An error will occur if dimensions are required for the analytical ledger and the source company does not include an analytical ledger, but the target company does. - For the column name, the COA name of the source company ledger will always display even if it is different than the target company.
When the invoice is posted, separate journals are generated in the source and target companies using the designated debit and credit accounts from Intercompany account mapping.
Prerequisites
Refer to documentation Implementation
Limitations
When the invoice is entered in tax-inc. mode and an additional or special tax code is present (entered or automatically loaded from the account), the amounts of the three tax levels must be entered manually.
Deleting intercompany invoices is allowed only if the SIVSUP - Invoice/journal deletion parameter (TC chapter, INV group) is set to "Yes" for all companies (source and target).
Screen management
Posting customer BP invoices involves three tabs containing the characteristics of each part of the invoice body.
Header
First, the key accounting information of the invoice must be entered:
- The site
- The invoice type
See the documentation on the customer invoice type.
This information determines the category of the document (invoice/credit memo/debit note/credit note), the automatic journal, the journal and the journal type that will be used when posting the document, - The document number (where a manual numbering range is authorized)
- The document posting date, by default that of its receipt in the folder
- The identification code for the supplier and the control account on saving the document.
This information defines:
- The invoice header
- The invoice lines
- The invoicing address
After this data has been recorded, click Post to:
- Pass the invoice in accounting. Click Journal to view the accounting document generated on the validation of the invoice.
- Automatically create an expense for each supplier BP invoice line, when the Fixed assets module is managed in the folder and when the conditions are met, the expense creation modalities are detailed below.
The Linked expenditures selection list displays the expenditures created that way and is used to access the management function of the selected expenditure by tunnel.
Block number 1
Site (field FCY) |
Enter the site code. The site must be a financial site. This determines the site and the company for the entry posting. |
Company (field CPY) |
Name (field CPYNAM) |
Invoice type (field PIVTYP) |
Invoice type code referencing the invoice category as well as the entry structure used upon accounting validation of the invoice. |
Document no. (field NUM) |
If the number is left blank, it will be automatically assigned upon validation. |
Block number 2
Accounting date (field ACCDAT) |
Enter a date to define the accounting date for the generated journal. This field defaults to today's date. This date is not necessarily the same date entered for the Source document. For example, for a supplier invoice, the Source document date reflects when the invoice was created by the supplier. In that case, the Accounting date would be different. |
Supplier (field BPR) |
In this field, enter or select the supplier for the invoice using the Lookup tool. To search using the auto select option, enter several characters of the supplier name or code and press the Tab or Enter key. The selection window opens with a list of suppliers based on those characters. The results include active and inactive records. Auto selection is available if the AUTOSEL – Auto selection parameter (SUP chapter, INT group) is set to Yes. |
Address code (field BPAINV) |
Name (field BPRNAM) |
Control (field BPRSAC) |
Enter the code for the BP (customer or supplier) control account initialized by default with the accounting code for the BP invoice. The initialization of the code for the Control field depends on whether or not the BP/Company tab is present in the BP record (GESBPR). |
Account (field SACACC) |
Intercompany invoicing example
One company (source) pays health insurance for itself and another company (target). A portion of the invoice is an expense of the source company and a portion of that invoice is due to the source company from the target company. When the invoice is entered in the system, the invoice lines in source Company A is as follows:
Company |
Site |
Legal |
Amount |
Description |
B |
B1 |
INSURANCE |
300.00 |
Using account in Company B |
A |
A1 |
INSURANCE |
700.00 |
Using account in Company A |
The invoice is entered in the source. When the invoice is posted in Company A, the resulting journal entries are as follows:
Company A
Site |
Legal |
Debit |
Credit |
Description |
A1 |
INSURANCE |
700.00 |
|
|
A1 |
DUE FROM COMPANY B |
300.00 |
|
Debit source GL account |
A1 |
ACCOUNTS PAYABLE |
|
1000.00 |
|
Company B
Site |
Legal |
Debit |
Credit |
Description |
B1 |
INSURANCE |
300.00 |
|
|
B1 |
DUE TO COMPANY A |
|
300.00 |
Credit target GL account |
Supplier Invoice with tax on line example
When the line associated with the intercompany transaction is taxable, the calculated tax should be based on the target company.
When the invoice is entered in the system, the invoice lines in source Company A is as follows:
Company |
Site |
Legal |
Amount |
Tax on line |
Amount |
B |
B1 |
INSURANCE |
300.00 |
30.00 |
330.00 |
A |
A1 |
INSURANCE |
700.00 |
70.00 |
770.00 |
The invoice is entered in the source. When the invoice is posted in Company A, the resulting journal entries are as follows:
Company A
Site |
Legal |
Debit |
Credit |
Description |
A1 |
INSURANCE |
700.00 |
|
|
A1 |
DUE FROM COMPANY B |
330.00 |
|
|
A1 |
Tax (line 2) |
70.00 |
|
Source Company COA for Tax accounting code |
A1 |
ACCOUNTS PAYABLE |
|
1,100.00 |
|
Company B
Site |
Legal |
Debit |
Credit |
Description |
B1 |
Tax (line 1) |
30.00 |
|
Target Company COA for Tax accounting code |
B1 |
INSURANCE |
300.00 |
|
|
B1 |
DUE TO COMPANY A |
|
330.00 |
|
Tab Header
Invoice characteristics
Some fields in the header are used to complete the invoice:
- Amount-tax and Amount +tax fields
The entry is optional. Upon entry of the amounts in the invoice lines, these are automatically displayed in the corresponding fields in the header. The following warning message displays during creation if the header fields have not been entered: 'Totals different from header'. - The link between a credit memo and the original invoice via this invoice number, or the link between the credit memo and the credit memo request number from the customer, etc.,
- A service period that indicates by start and end date ranges, the part of service to be taken in advance for the next period or fiscal year. These fields are only activated if the SVC - Periodic accruals activity code is active. The expense or revenue to be taken in advance are generated in the Closing accruals (CPTSVC) function.
- The default analysis that is applied to the payments for the BP accounts. It is possible to define the default dimensions in the invoice header (see the Default dimensions).
Open item characteristics
The remaining fields are used to characterize the payment conditions for the invoice:
- Pay-by BP
- Choice of the payment due date
- Payment approval level (accessible based on the FLGPAZ - Management of payment approvals parameter value)
- EU invoice flag, used to condition the generation of VAT entries on an intra-community acquisition. If it is an EU invoice, the Tax inc. amount calculated in the invoice lines is always equal to the Ex-tax amount, but VAT postings are generated.
- For the 1099 form (specific to the United States), if the 1099 check box is selected, the invoice will include the elements to be declared as per the 1099 declaration. There is no control on the value. This check box is only available if the supplier is selected for 1099 management,
See the documentation on suppliers for further information - For the management of open item statements
Once the invoice has been saved, you can click the Open items action to view the open items and the payment stage.
The Status field indicates the status of the invoice with respect to the accounting validation. The Pending status can be selected in order to disable the access to the Validation action and to the invoice selection in the global process.
The status must be set to Pending for the invoice to be posted manually or globally. This modification is carried out either manually, on a case-by-case basis, or in a more global manner via the appropriate processing.
See the documentation on Invoices on hold for further information.
Detail
Source document date (field BPRDAT) |
Enter the invoice date. This field defaults to today's date. |
field TYPVCR |
field CLSVCR |
field SCUVCR |
field SEQVCR |
Source document (field BPRVCR) |
This field is used to record the number or the reference of the source invoice. |
Currency (field CUR) |
This field indicates the invoicing currency. All amounts are entered in this currency. |
Rate (field RAT1) |
field LABEL |
field RAT2 |
field CURMLT |
Amount - tax (field AMTNOT) |
This amount is only a control amount that will be compared the line total during the recording. This amount is mandatory when the HEAAMTBPS – Supplier inv. header amt. ctrl parameter (TRS chapter, INV group) is set to Ex-tax and Tax -incl. amounts to be entered. |
Amount + tax (field AMTATI) |
Invoice number (field INVNUM) |
This invoice is the one to which the credit memo is allocated. Depending on the value of the INVCAN - Cancellation invoice parameter (TC chapter, INV group), thedocument in progress can be of the 'Cancellation invoice' type. In this case, the credit memo and invoice are matched, regardless of the value of the LETAUTCNO parameter. |
Project (field PJTH) |
VCS number (field BELVCS) |
Field linked to the Belgian legislation. Reminder : the structured communication consists in specifying a single identifier on the invoices that will be used in all the banking exchanges. The encoding number is made up of 12 numeric characters:
In the case of purchase invoices and supplier BP invoices, the encoding number is controlled and can be entered. It is performed:
In case of a site modification, the display of the 'VCS number' field is reinitialized. |
Original document no. (field ORIDOCNUM) |
Block number 3
Status (field STA) |
No help linked to this field. |
Tax rule (field VAC) |
Enter the VAT management type associated with the supplier invoice. This field is automatically entered if a tax rule is specified in the record of the supplier of the current invoice. This is used, among other things, to obtain a print conditioned by the type of legislation. |
Supplier amount type (field PURPRITYP) |
This flag is initialized based on the business partner. It determines if the amounts on the invoice lines are including-tax or excluding-tax amounts. It is only possible to choose between Include tax or Exclude tax when creating the invoice.
|
Field 40 - reason (field FLD40REN) |
Field subject to activity code: KPO - Portuguese localization |
Field 41 - reason (field FLD41REN) |
Field subject to activity code: KPO - Portuguese localization |
Open items
VAT reverse charge (field CEEFLG) |
Indicate whether the tax rule is subject to autoliquidation. |
Fees declaration (field DAS2) |
This field indicates if the entry generated by the invoice is to be taken into account in the declaration of fees or not. |
Statement (field XSOI) |
No help linked to this field. |
Pay approval (field XFLGPAZ) |
This field is used to pre-enter the field "payment approval" of the generated open items. |
Payment
Pay-to (field BPRPAY) |
Enter the invoice date. This field defaults to today's date. |
Address code (field BPAPAY) |
Due date basis (field STRDUDDAT) |
This is the date from which the payment schedule is calculated. |
Payment term (field PTE) |
This field indicates the payment conditions that will be applied in order to determine the invoice schedule. The latter can be manually modified later on. |
Due date (field DUDDAT) |
Discount/Late charge (field DEP) |
Code used by default for the current BP to identify a series of early discount and late charge rates (up to 12) to be applied to a payment according to a number of days early or days late with respect to the open item date. |
Comments (field DES) |
1099 form (field FRM1099) |
The 1099 form type indicates that a supplier is reportable to the Internal Revenue Service for payments made. Possible valid values are: None. Misc, Dividend or Interest. This value defaults from the supplier to the invoice, but can be changed. |
1099 box (field BOX1099) |
Default box number with respect to which payments must be printed on the 1099 record. Box numbers vary according the 1099 record at use. This value defaults from the supplier to the invoice, but can be changed. Inactive 1099 boxes are not available for selection. |
Amt. subject to 1099 (field AMTSUBJ109) |
Invoice amount subject to a 1099 declaration. This amount is automatically calculated based on the sum of the invoice ex-tax amounts for the detail lines having the 1099 field set to Yes. |
Grid Analytical
No. (field NUMLIG2) |
Dimension type (field DIE) |
Dimension (field CCE) |
The dimensions entered here will be used as default values for invoice lines. |
Tab Lines
This grid displays each of the invoice lines from an accounting point of view:
Nature
If the account is subject to dimensional accounting, it is necessary to define its nature. At general accounts level, it is possible to define a nature linked automatically to an account. The nature field cannot then be modified.
See the documentation on General accounts for further information.
On the other hand, if a nature screen has been defined, it is possible to choose a different analytical nature conforming to the screen.
Dimension types
If the accounting amount is not distributed over several analytical dimensions, the 'Allocation' field cannot be assigned. The entry is achieved directly in the following columns, in the dimension concerned, for each of the dimension types.
Default dimensions can be defined at the level of the nature, but those defined by the default dimension processing have priority.
See the documentation on the default dimensions.
CAI assignment
CAI number (field CAI) |
Validity date (field DATVLYCAI) |
Grid Details
No. (field NUMLIG) |
Site (field FCYLIN) |
The site of each line can be different from the header site. In this case, the generated journal will be balanced site by site using inter-site link accounts. Specificities linked to intercompany invoices (GESBICI and GESBISI functions protected by the activity code INTCO - Intercompany transactions):
|
Company (field CPYLIN) |
Ctrl. (field SAC) |
No help linked to this field. |
BP (field BPRLIN) |
The choice of accounting allocation is determined by:
|
Settlement discount (field FLGDEP) |
This field is used to specify if an invoice line is subject to discount.
|
Amount - tax (field AMTNOTLIN) |
Enter in this field the ex-tax amount of the recorded operation. |
1099 (field FLG1099) |
The 1099 flag is used to indicate whether a line is submitted to a 1099 declaration. If the supplier must be subjected to a 1099 declaration, the default value of this line will then be positioned to Yes. If a line for this supplier is not subject to 1099, then this flag can be changed to No and the line will not be included in reportable 1099 amount. |
Tax (field VAT) |
When the account on the line is liable for tax, the tax field is accessible for entry. It is initialized with the tax code associated with the account or with the tax code associated with the rule. |
Tax amount (field AMTVAT) |
Amount + tax (field AMTATILIN) |
No help linked to this field. |
Purchase type (field PURTYP) |
Depending on the journal setup, a different accounting process can be performed based on the purchase type. |
Withholding tax (field RITCODSRC) |
Deduction at source code. |
Comment (field DES) |
It is possible to manually enter a comment on the line. By using:
|
VAT declaration no. (field DCLEECNUM) |
This field is displayed only if the following conditions are met:
This field is initialized:
It can still be modified if it is set up to accept entries at entry transaction level and if the invoice is not validated. |
Unit (field UOM) |
Quantity (field QTY) |
Upon setting up an analytical nature (Common data/Accounting Tables/Analytical/Natures), whether there is work unit entry is defined, then a default value is attributed to it by specifying its default value (in reporting currency). |
Project (field PJTLIN) |
After invoice validation, the project reference the invoice line is allocated to can no longer be modified. |
Cost type (field PCCCOD) |
Distribution (field DSP) |
Defined here are the allocation methods for the line amount on the different dimensions of each dimension type. These methods are defined as follows:
Example: on a basis of 100, a coefficient of 10 will be read as 10 %. But, on a basis of 50, a coefficient of 10 will be equivalent to 20 %. |
field CCE1 |
The setup determines if the analytical dimensions can be modified. They are initialized based on the setup of the default dimension. In creation mode, if no order line has been entered and the project code is modified, the analytical dimensions are reset based on the setup of default dimensions. In creation mode, as in modification mode, if an order line is entered and the project code is modified, the analytical dimensions are not reset. |
Totals
Discount basis (field BASDEP) |
The discountable base is only displayed if the two following conditions are met:
The discountable basis depends on:
If the user wants to add a discount after saving the invoice, the discount code addition can be performed via button [Open items]. Fields "Discount" and "Discount basis" will be hidden and the discountable basis will be equal to the tax incl total. |
field CUR3 |
Total excluding tax (field TOTNOT) |
field CUR1 |
Total including tax (field TOTATI) |
field CUR2 |
Account
field AFFICHE |
Supplier amount type (field PURPRITYP) |
Account inquiry
AFC/GESBIC/40/405
Statistical codes
AFC/GESBIC/40/410
Periodic accruals
AFC/GESBIC/40/415
Account structure
AFC/GESBIC/40/420
Supplier notes |
Select this option to display the note(s) associated with this supplier. This window could open automatically depending on the setup defined when creating the notes. Notes are limited to a screen inquiry and cannot be printed. See the Notes documentation for more information. |
Intercompany dimensions |
The Intercompany dimensions window will automatically appear if different dimensions are found between the source and target company, or by selecting Dimensions from the right-click menu on the line. Up to 20 dimension types can be displayed in the Intercompany dimensions window. An error will occur if dimensions are required for the analytical ledger and the source company does not include an analytical ledger, but the target company does. |