Coding and tax
Coding
Section titled “Coding”A PO invoice takes its coding from the PO lines. A non-PO bill (utilities, leases, services) is coded from that supplier’s history: the fund, cost center, account and, for Oracle, the project and task its past bills were coded to.
Open the invoice’s Coding tab to see:
- The suggestion, line by line.
- The past bills it learned from.
- Whether it was applied automatically (it was confident enough) or is waiting for you, and who applied it.
Change any line and save; your change becomes part of the history for that supplier’s next bill.
The Tax tab shows each line’s taxability and the rate for the place it was delivered to.
- Undercharged: when a supplier bills too little sales tax (common with out-of-state suppliers), Spend accrues use tax for the difference.
- Overcharged or tax on exempt items: the invoice stops so you can ask the supplier for a corrected bill.
Sales and use tax (in the sidebar) holds the use tax return by jurisdiction, its GL journal, and the list of bills taxed wrong.
Rates come from the built-in rate table, the state rate file, or your tax engine (Avalara or Vertex), as your administrator sets up.