Posting Profiles & GL Configuration

Posting profiles are the rules that tell your accounting system which GL accounts to debit and credit for every type of transaction. They are the invisible engine behind automatic double-entry accounting -- ensuring that when you post an AP invoice, the system knows to debit the expense account and credit accounts payable without anyone specifying those accounts manually each time.

The Relationship Chain

Every transaction type in the system (AR invoices, AP payments, bank fees, payroll entries, and dozens more) is mapped to a posting profile. That posting profile defines exactly two things: which GL account to debit and which to credit. This creates a clean, auditable chain from business event to journal entry.

For example, when you post a customer invoice, the system looks up the AR_INVOICE transaction type, finds its mapped posting profile (typically called "Customer Receivables"), and uses that profile to generate the journal entry: debit Accounts Receivable, credit Sales Revenue. This happens automatically on every transaction, eliminating the risk of manual posting errors.

Why Posting Profiles Matter

Without posting profiles, every transaction would require someone to manually select the correct debit and credit accounts. That manual process is slow, error-prone, and inconsistent. With posting profiles, you configure the rules once and the system applies them reliably thousands of times.

When your chart of accounts changes -- perhaps you split a revenue account into two or rename an expense category -- you update the posting profile once and every future transaction uses the new mapping. Historical transactions retain their original postings, preserving your audit trail.

Configuration and Control

You can view all posting profiles for any legal entity, filtered by profile type (customer, vendor, banking, payroll) or searched by name and account number. Each profile shows its debit and credit accounts with their full names, making it easy to verify that your GL mappings are correct.

Creating or updating posting profiles flows through the same workflow system as other configuration changes. The system validates that the referenced GL accounts exist and are active, preventing broken mappings that could cause transaction posting failures.

Practical Applications

Posting profiles handle the full range of accounting scenarios. Separate profiles exist for accounts receivable versus accounts payable, bank deposits versus withdrawals, payroll expenses versus payroll liabilities, and foreign exchange gains versus losses. When you add new transaction types to your system, you create matching posting profiles to complete the configuration.

This declarative approach to GL mapping means your accounting logic is explicit, documented, and auditable -- not buried in procedural code or spreadsheet formulas.