PayPoke · owner guide

Enter customer and invoice details

The first-invoice setup stores one initial invoice with your sender details. You can also add multiple invoices for the same customer using the invoice form or CSV import. PayPoke stores these details; it does not create or send invoices or collect payments.

01 · Choose a path

Set up once, then add invoices

First invoice

Save your initial invoice setup

First invoice saves or updates one first-invoice setup per account. It includes sender details, one customer, and one invoice for this setup; it is not a one-invoice-per-customer cap. Add more invoices for that customer separately. Saving requires sign-in and an active PayPoke subscription.

Individual entry and CSV

Add customer and invoice records

Add customers from Dashboard → Customers, then create multiple invoices for a customer from Dashboard → Invoices. You can also import multiple customers and invoices from CSV. These workspace tools require sign-in and active PayPoke access.

02 · First-invoice setup

Details saved in the single setup

The setup page asks for your business or sender name, sender email, and sender address; one customer name and recipient email; a positive USD amount; a due date; and whether it is paid or unpaid. This is one saved setup; other invoices stay as separate records and may use a different due date and payment status.

Open First invoice setup

03 · Customer and invoice CSVs

Import customers before invoices

In Dashboard → Import data, choose the customer target first. Its required columns are name,email. Then choose the invoice target with invoiceNumber,customerEmail,amount,dueDate,paymentStatus. Each invoice row must refer by email to a customer already in the active workspace, so import customers before invoices.

An unpaid CSV-imported invoice enters the same enabled pre-due and overdue reminder checks as an individually entered invoice. Each invoice is evaluated separately, and marking one paid removes it from future automatic reminder candidates without affecting other unpaid invoices for that customer.

Customer fields

Both name and email are required. The email must be valid.

Invoice fields

Invoice number, customer email, amount, and due date are required. Amounts must be positive USD decimals with up to two decimal places. Due dates must be real calendar dates in YYYY-MM-DD format. Payment status accepts paid or unpaid; if omitted or blank, it defaults to unpaid.

04 · Check and confirm

Review the file before anything is created

The importer checks your file first. No records are created by this flow until you explicitly confirm the import.

  1. 1

    Choose a CSV

    Use a UTF-8 file up to 10 MiB. Select a comma or semicolon separator.

  2. 2

    Map the columns

    Match each source column to the customer or invoice field it supplies.

  3. 3

    Select Check file

    Inspect the summary, row preview, and any reported issues. Checks cover required fields, formats, malformed CSV shape, and repeated customer emails or invoice numbers within the file. Missing invoice customers are reported as invalid rows too.

  4. 4

    Confirm with Import N

    If any rows are invalid, the import cannot be confirmed. Correct the source file and check it again. When the preview is valid, select the explicit Import N button to create the new records.

For valid rows, a customer email or invoice number already present in the active workspace is counted as already present and skipped. These customer and invoice targets are create-only; they do not update existing records.

Open Dashboard → Import data