Management of Posting Rules

This guide covers the management of posting rules. You can find the posting rules management view in Netvisor by navigating to Financial Management > Accounting Settings > Posting Rules. 

You can create a rule for the posting of bank statements, which automatically generates a posting proposal for similar transactions. The posting rule can be displayed on the bank statement and in the sales payment list, where transactions can be posted using the rule.

To create a posting rule, you must have at least editing rights for the bank statement and basic accounting functions. 

Add a new posting rule: You can create a new rule from the "Add a new posting rule" link at the top of the page.
Edit: You can edit the rule from the Edit column xx-link. The editing contains the same information as when creating a new one.
Delete: You can delete the rule from the Delete column xx-link.

Posting rule details and fields

Posting rule name: Name the rule so that the name directly indicates what the rule is intended to post.

Used only in transfers: With this option, you can create a posting rule, but the transaction must still be manually handled from the bank statement using the rule.

Targeted amount: This field is the first of three targets. If a specific amount, such as 1234.56 euros, repeatedly appears on the bank statement, the amount field can be used as a target. If the transaction amounts vary, this target cannot be used.

Payment subject code: The second target field. This target is absolutely reliable. On a machine-readable bank statement, each line has its own transaction code, i.e., payment subject code. Bank service fees always appear with a specific code on the bank statement, other transactions do not use this code. Transfers also have their own code, etc. You can easily view the transaction code by opening the bank statement edit view and clicking the "Fetch posting rules" link (even if you don't have any rules yet). After clicking the link, the system displays the payment subject code for each line. Copy the code from there and use it in the posting rule if necessary.
If you are creating a posting rule for bank service fees, note that there are both taxable and non-taxable fees. Create the rule based on which type is more prevalent on the bank statement, manually handle exceptions with the Post tool, and then use the rule for the rest.

Payment name specification: The third target. This field is case-sensitive, meaning "RENT" must be in uppercase in the name specification, "Rent" or "rent" will not work for targeting. This can be used, for example, in posting payroll transactions, where the employee's name is a functional target (if the HRM section is not in use and payroll is calculated in another program).

Bank account: If the rule is used through the bank statement, the bank account must match for the rule to be selectable.

Voucher row posting specification: You can provide the desired posting specification here. When processing transactions through the bank statement, this specification will appear in the voucher's row specification field. Additionally, it will be followed by a dash and then the bank statement transaction rows. Example bank statement with a 150 euro transaction processed with a bank statement rule with posting specification: Desired posting specification

The voucher will appear as follows:

If the posting rule is used in the sales and payment section and there is a posting specification here, the row specification will be based on what is entered in the posting specification field. This overrides the posting rule's posting specification. The sales and payment view cannot use an empty posting specification. 

Cost objects: With the posting rule, you can choose whether the rule creates a cost object for the generated voucher. To make the cost object visible, they must first be created in the cost object management.

Keywords: posting rule, posting rule management

Did you find it helpful? Yes No