Create and Manage Bills

Use this bills front door to choose the right payables workflow before creating, paying, importing, matching, voiding, or correcting a vendor bill.

Bill row actions for payment history and linked journal review

Use This Page When

Bills can affect vendor balances, expense accounts, payment timing, and later review work. Start here when you need to decide which bill page fits the job in front of you.

Choose This Path If

Goal Use Check First
Enter a new vendor bill Create bills Vendor, Pay from, due date, line accounts, and bill status
Record a full or partial bill payment Record bill payments Bill balance, Pay from, payment date, and whether a bank row should be matched
Import grouped bill rows from a file Import bills Vendors, line accounts, duplicate bill numbers, and Pay from routing
Match a bank withdrawal to an open bill Match bank transactions Pending bank row, open bill, vendor, amount, date, and difference
Void or correct a posted bill Void or correct bills Active payments, linked journals, bill status, balance, and reversal date
Choose a payables correction path Review common payables workflows Whether the issue belongs to vendor setup, bill entry, payment, banking, or journal review

Before You Commit

  • Confirm the active company before creating or changing bill records.
  • Review whether Pay from should use an Accounts Payable control account or a cash, bank, or credit-card settlement account.
  • Review line-level Account values before saving or importing.
  • Check bill balance before recording payment or voiding.
  • Review payment history before reversing or correcting a bill with activity.
  • Treat posted-save prompts, void confirmation, and paid-now routing as accounting-sensitive choices.

What Not To Assume

  • Paid status is not the same thing as matching a bank withdrawal.
  • Default expense account is not a substitute for reviewing line-level bill accounts.
  • A bill payment and a bank match can describe the same cash movement; avoid recording both unless both are intentionally required.
  • Voiding a bill is not deleting it. A supported void preserves the bill and reversal history.
  • Vendor defaults seed values; they do not remove the need to review each bill.

Practice And Examples