Skip to main content
Accounting rules define which General Ledger (GL) accounts Hyperline uses when posting journal entries. Each rule belongs to a category that matches a specific billing event, and can be scoped to a subset of products, customers, currencies, or payment methods using filters.

​
Rule categories

Rules of all categories can coexist in the same ledger. Revenue recognition settings are resolved at invoice posting time alongside the Invoice posted rule — they are not triggered by a separate event.

​
Account mappings

Each rule specifies which GL account to use for each role in the journal entry. The available account roles depend on the rule category: Invoice posted
  • Accounts receivable
  • Revenue account
  • Deferred revenue
  • Output tax / VAT
  • Discount account
  • Deferred discount account
  • Contra-revenue account
  • Customer credits account
  • Bad debt / allowance for doubtful accounts
Invoice settled
  • Cash / bank account
  • Payment clearing account
  • Provider fees expense account
  • Payment processing fees account
  • Accounts receivable (cleared on settlement)
Credit note created
  • Customer credits account
  • Contra-revenue account
  • Deferred discount account
  • Revenue account (reversed)
  • Output tax account (reversed)
  • Accounts receivable (for unpaid invoices)
Revenue recognition
  • Revenue account (when recognised)
  • Deferred revenue (until recognised)
Accounting software sync Accounting software sync rules map Hyperline billing records to the accounts expected by your connected accounting provider. When Hyperline sends a record to an external accounting provider, the resolved account is converted to the provider account code or internal account ID required by that provider. For invoice sync rules, the main Revenue account is used for regular invoice and credit note lines. The optional Bad Debt Expense account is used by providers that create a write-off record for uncollectible invoices. For example, NetSuite uses this account on the write-off Credit Memo created and applied to the original invoice when an invoice is marked uncollectible. Accounts can be created manually in Hyperline or fetched from your accounting provider by syncing the ledger’s chart of accounts. See Chart of accounts.

​
View the rule tree

Accounting > Settings > Rules displays all rules grouped by category, showing which rules would apply and in what order for each event type. This is useful for auditing your rule configuration before going live.

​
Filters

Rules can be scoped using one or more filters. Available filters depend on the rule category. When a billing event occurs, Hyperline evaluates all matching rules and applies them in priority order. Invoice posted Invoice settled Credit note created Revenue recognition An empty filter matches everything — rules with no filters act as catch-all defaults.

​
Criteria reference

The rule form can use the following criteria, depending on the selected category:

​
Priority and fallback

When multiple rules match the same billing event, Hyperline applies them using a priority overlay:
  1. All matching rules are collected and sorted by priority (ascending)
  2. Rules are applied in order — each rule overrides only the account roles it explicitly defines
  3. The rule with the highest priority number wins for any given account role
This means you can define a low-priority default rule that covers all products, then add higher-priority rules to override specific account mappings for individual products or customer segments.

Example 💡

You have a default invoice posted rule (priority 10) that maps all revenue to account 4000 – Revenue. You then add a second rule (priority 50) scoped to a specific product that maps its revenue to 4100 – Usage Revenue. When an invoice is issued for that product, Hyperline uses 4100 for that product’s line items and 4000 for everything else.

​
Tiebreaker at equal priority

When two matching rules share the same priority, Hyperline picks the more specific one:
  1. A rule scoped to customers wins over a rule scoped to products
  2. A rule scoped to products wins over a rule with no customer or product filter
  3. If both rules are equally specific, the rule created first wins
Only customer and product filters affect this tiebreaker. Other filters (coupons, currencies, countries, intervals, payment methods) do not — use distinct priorities to disambiguate them.

Example 💡

Two rules both have priority 10:
  • Rule A scoped to customer cust_123
  • Rule B scoped to product prod_456
For an invoice line where both rules match, Rule A wins because customer-scoped rules take precedence over product-scoped rules at the same priority.

​
Add a rule

Go to Accounting > Settings > Rules and click Add rule.
  1. Select the rule category
  2. Assign a priority (integer; higher wins)
  3. Configure the account mappings for each role
  4. Optionally add filters to scope the rule

​
Edit and delete rules

Click the edit or delete icon next to any rule in the rule list. Deleting a rule does not affect already-posted journal entries.