Current Behaviour: When a Payment Method Code is set up with a Bal. Account Type (e.g., Bank Account) and Bal. Account No., this balancing account logic only works when posting through Purchase Invoice documents. The system automatically creates the vendor invoice entry and the offsetting bank/payment entry in one step — which is the expected and desired behaviour.

However, when creating a vendor invoice through a General Journal, Purchase Journal, or Standard General Journal, the Payment Method Code is either ignored or treated as informational only. The balancing account from the Payment Method Code is not applied, and no automatic bank/payment entry is created. This forces users to manually add a separate payment line with the correct bank account, increasing the risk of errors and missed bank entries.

Requested Enhancement: Extend the Payment Method Code balancing account logic to all journal posting methods — including General Journals, Purchase Journals, and Standard General Journals — so that the system automatically creates the offsetting bank/payment entry, consistent with how it works on Purchase Invoice documents.

Business Impact:

• Reduces manual data entry and the risk of incomplete postings
• Ensures consistency across all posting methods (documents vs. journals)
• Prevents missed bank ledger entries, improving bank reconciliation accuracy
• Supports organizations that rely on journals for bulk or recurring vendor transactions rather than individual Purchase Invoice documents

Note: This is also in relation to an idea raised by Sabrina Marquard on 1/27/2020 "Payment Method and posting related payment in G/L Journals":