Post miscellaneous charges to a general ledger account
If you are posting miscellaneous charges to a general ledger account, Kofax AP Agility creates a separate general ledger entry for each miscellaneous charge.
A general ledger entry consists of the following components:
-
A general ledger account code representing the type of expense.
-
A cost object, such as a cost center, an internal order, a profit center, or a project.
-
A tax code.
To determine the general ledger account code, Kofax AP Agility looks into a custom database table. If an entry exists for the invoice company code and the miscellaneous charge code, then this is the general ledger account code that Kofax AP Agility uses. If no entry exists, or the Validate From DB setting is selected in the Settings > Invoice Processing > Capture Profiles > Misc Charge Settings > Misc Charge Settings, then the default general ledger code for the miscellaneous charge group is used.
The cost object is determined as follows:
-
If the Get Cost Object From PO Line setting is selected Settings > Invoice Processing > Capture Profiles > Misc Charge Settings > Misc Charge Categories tab, the cost object is lifted from the first paired invoice line that uses either a cost center, a profit center, an internal order, or a project.
-
If a profit center or cost center exists in the custom table, this is used as the cost object.
-
The default cost center/profit center in the Default Cost Center / Default Profit Center columns in the Settings > Invoice Processing > Capture Profiles > Misc Charge Settings > Misc Charge Categories is used.
The tax code is determined as follows:
-
If an entry exists in the custom table for the invoice company code and miscellaneous charge category, this tax code is used.
-
The tax code is lifted from the first paired invoice line item.
-
The tax code set in the Default Tax Code setting in the Settings > Invoice Processing > Capture Profiles > Misc Charge Settings > Misc Charge Categories is used.
-
For countries and ERP systems that use tax jurisdictions, the tax jurisdiction code is derived from the first paired invoice line.
If the general ledger account is not relevant for tax postings in the ERP system, a double asterisk (**) must be entered into the tax code column in the table. This passes a blank tax code and a blank tax jurisdiction code downstream.
If the custom table lookup is activated but communication does not succeed either due to missing or incorrect configuration or database unavailability, the document export fails.
A sample configuration for posting miscellaneous charges as general ledger entries is shown in the following table. This must be entered as a row into the Settings > Invoice Processing > Capture Profiles > Misc Charge Settings > Misc Charge Categories for the selected profile ID.
Setting |
Value |
---|---|
Index |
1 |
Type |
FREIGHT |
Code |
F |
Header Field |
Postage |
Alias |
FREIGHT, DELIVERY, CARRIAGE, UPS, TRANSPORT |
Line Type |
|
Always Book To Unplanned |
FALSE |
Always Book To Planned |
FALSE |
Valid Conditions |
|
Always Book To GL Account |
TRUE |
Book To Unplanned If No Planned |
FALSE |
Book To GL Account If No Planned |
FALSE |
GL Account |
1000 |
Get Cost Object From PO Line |
TRUE |
Default Cost Center |
1000 |
Default Profit Center |
2000 |
Default Tax Code |
I0 |
With the above configuration, if the custom table is not used, Kofax AP Agility books the miscellaneous charge as a general ledger entry using general ledger account 1000, with the cost object and tax code from the first paired invoice line. If no cost object exists against the first paired invoice line, then cost center 1000 and profit center 2000 are used. If no tax code exists against the first paired invoice line, tax code I0 is used.