submit-reimbursement

To submit an out-of-pocket reimbursement, you provide a base64-encoded receipt, which creates a draft that you review for missing items like amount, merchant, and fund allocation before final submission. The process iteratively resolves missing fields using suggested memos and coding until all requirements are met.

Your receipt needs to be base64-encoded content, typically a PDF, to initiate the reimbursement submission workflow. The system uses this base64-encoded receipt content to create a draft reimbursement linked to a generated receipt_uuid for tracking and approval processing.

You can automate expense reporting while ensuring required fields are completed because the reimbursement submission process checks for missing_items after edits and iteratively fills required fields. It uses suggested memos, funds, and accounting categories when available to resolve gaps before allowing submission.

Yes, the reimbursement submission process requires explicit user confirmation before sending for approval. It enforces a guardrail step that displays the populated amount, merchant, memo, fund allocation, and accounting categories to ensure all details are verified and prevent mistakes that could delay approval.

If your reimbursement draft is missing fund allocation or accounting categories, the system checks the missing_items response after edits and iteratively fills the required fields. It uses suggested memos, funds, and coding when available to ensure the reimbursement is complete before you submit it for approval.