Counter Accruals

The system automatically creates a counter accrual when an accrual is issued between two own companies. The logic applies across different object types, each of which uses its own pair of counterpart fields:

  • Invoices: Issued By and Payer.

  • Obligations: Debtor and Creditor.

  • Rewards: Issued By and Beneficiary.

When both sides of any of these field pairs are marked as Own Companies, the accrual created by one entity becomes income for that entity and an expense for the other. To ensure correct internal accounting and prevent the expense side from being lost, the system generates a counter accrual with the opposite direction.

Creation Logic

When an accrual meets the internal-settlement criteria, the system creates a counter accrual based on the original one. The counter accrual is a mirrored version of the initial record but with an opposite direction.

Additional rules apply depending on the accrual type:

  • Freight Invoices & Disbursement Accounts: The counter accrual is created without an Invoice Number.

  • Accounting accruals (Invoice, Reward, Obligation): The Subtype is cleared for Miscellaneous tabs.

After saving the original accrual, a notification is displayed:
"Counter [direction] accrual has been created for internal settlements between own companies"

Update Logic

If an accrual and its counter accrual exist as a linked pair, updates to one record lead to updates in the other. However, the following fields and tabs are not synchronized during updates:

  • Remarks tab;

  • Accrual name;

  • Subtype;

  • Payments tab (list of payment records).

Business Rationale

The feature ensures accurate internal accounting between companies operating within the same system.

For instance, if only one company operates in the system, an outgoing accrual issued by that company is recorded as revenue. If a second company (the Payer) is also active in the system, that same accrual must simultaneously appear as an expense for the payer.

Without the counter accrual, the expense side would not be recorded, causing inconsistencies in internal financial tracking.