Bills upload

Uploading bills to Tipalti via CSV or API involves the following checks and steps:

Check if the payee exists and the payee's status

Mandatory for ERP integration.

• Recommended: Check before uploading bills, to avoid creating an empty payee profile with "Not Payable" status.
• Mandatory if ERP integration is in place: Check the status to avoid payee/bill sync errors between Tipalti and your ERP.

Bill uploads to Tipalti (via CSV or API)

• Self-billing (no approval): Pending Payment.
• Self-billing (payer approval): Include the approver details in the CSV or API call.
• Self-billing (payee approval): "Release" the bill after upload so the payee can approve it via the Supplier Hub or iFrame.
• Supplier invoices (payer approval): The payee can upload the bill via the Supplier Hub or iFrame, or email the bill for scanning.
• GL account selection is possible if you're integrated with an ERP.
• You can also pass the "approver" value via the API call or CSV.
• You can test all of these workflows in Sandbox, except for the scanning feature under Supplier Invoices.
• API call: CreateOrUpdateInvoices

Edit bills

• You can edit a bill before or after approval, either manually via the Tipalti Hub, via an API call, or via the CSV upload "Action" column.
• Retracting an approval sends the bill back to "Pending AP Action" (the only allowed status for this).
• For the approval workflow, you can't bypass the approval step via API call (going from "Pending AP Action" directly to "Pending Payment" isn't possible). You can set it to "Pending Approval" by passing approver values in the API call.
• You can set a default to release the bill to an approver, as long as the approver is specified.
• If you're using the approval workflow, you must pass approver values in the API or CSV upload.
• API call: CreateOrUpdateInvoices

Retrieve bill status

Bill statuses:

• PendingAPReview (default)
• PendingApproval
• PendingApAction
• PendingPayment
• SubmittedForPayment
• Disputed
• Deleted