See the compliance workflow before creating an account.

Prepare your first invoice Fictional records in the real application; synthetic narration. Start with the work you actually delivered. This recording uses fictional provider and student records in the real Get ESA Paid application. Add the provider and student details on the invoice screen. Choose the actual program before reviewing its requirements. You do not need to leave this task to finish setup. Enter the service date, subject, description and agreed rate. Here, one reading session costs seventy five dollars. A correct total alone does not establish expense eligibility. Save and review the invoice. The submission workspace brings together the draft, common checks and supporting evidence. Review the official program instructions before using its payment portal. Your saved invoice is the starting point for the next billing cycle. Try the workflow with your own records at get ESA paid dot com.

Prepare the next billing period Fictional records in the real application; synthetic narration. Keep the useful details from a previous invoice without accidentally billing last month's dates. This example uses a fictional saved tutoring invoice. Choose prepare next billing period. The new draft carries the student and service details forward, with a suggested invoice number and blank service dates. Enter the actual date for the next completed session. Review the quantity and rate, and make sure the service has not already been billed elsewhere. Save and review the new invoice. The previous invoice remains a separate record. This is a reviewed draft workflow, not unattended recurring billing or automatic payment collection. Come back for your next billing run and check whether the workflow saves you repeated setup. Start your trial at get ESA paid dot com.

Preserve an invoice correction Fictional records in the real application; synthetic narration. When an invoice needs a correction, keep the original evidence. This fictional example changes an entered hourly rate from seventy five dollars to sixty dollars. Open the invoice workspace and choose correct invoice. The application prepares an editable correction instead of silently replacing the original document. Update the incorrect field and write a factual correction note. Explain what changed and why, using the actual service or agreement as your evidence. Save the correction. Review the new version and its preflight result. Follow the program's amendment instructions; saving here does not resubmit a claim to a payment platform. Keep the correction, supporting documents and eventual payment linked. Try the invoice-record workflow at get ESA paid dot com.

Match a payment CSV to an invoice Fictional records in the real application; synthetic narration. An invoice and a deposit are different records. This fictional payment file allocates sixty dollars to one saved invoice, using its exact invoice number. From your invoice list, open the payout CSV import. Check the required columns, and map different export headings when needed. This upload contains synthetic data only. Select the file and choose validate and import. This action writes the valid matches; it is not a separate preview-and-confirm screen. Always inspect your file before importing. Open the matched invoice workspace and check the payout history. Confirm the amount and reference against your actual bank and payment records before treating the transaction as settled. Keep unresolved balances visible and investigate ambiguous matches. Start with the free templates or try saved invoice records at get ESA paid dot com.