Skip to content

AR Email Configuration

The AR Email channel creates outbound sales invoices by email. Send a sales invoice PDF (or supported file) to a dedicated mailbox; Tapr polls the inbox, extracts the attachment, and creates a Sales Invoice in Out Docs.

This is AR intake into Out Docs — not the PEPPOL send step. After the invoice appears, review it and Send to Customer as usual.

For all outbound creation options, see Creating & Sending Sales Invoices.

  • Teams already email PDFs from billing or desktop tools
  • Volume similar to Upload Invoice (roughly 5–20 per month)
  • Same AI extraction path as upload, without opening Invoice Manager for each file
  1. AR Email enabled in Tapr Settings (below)
  2. AI provider with your own API key (BYOK) for plain PDFs and images — same requirement as Out Docs upload. Structured e-invoices with embedded XML can extract without AI.
  3. Legal entity and PEPPOL setup ready before you send extracted invoices

Configure AI under Tapr Settings → AI & Extraction. See AI Provider Comparison.

  1. Open Tapr Settings in the Frappe desk (see Tapr Settings Overview)
  2. Open the AR Settings tab
  3. Check Enable AR Email

AR Settings tab

AR Settings: enable the mailbox, note the assigned address, set the password.

The system provides pre-configured, read-only server parameters:

FieldValuePurpose
IMAP Servermail.tapr.chTapr managed mail server
IMAP Port143Standard IMAP port
Use STARTTLSYesEncrypted connection
FieldPurpose
Username/EmailYour AR email address (assigned by Tapr)
New PasswordUpdate credentials as needed
IMAP FolderFolder to monitor
Process all emailsReprocess more than unread mail if needed
  1. Enter the new password in New Password
  2. Click Update AR Password
  3. Credentials are stored securely for IMAP access

Use Test AR Email Connection to validate login. Optionally run Fetch AR emails now or View AR Mailbox.

  1. A user emails the AR address with a sales invoice attachment
  2. The scheduler (or Fetch AR emails now) opens the AR mailbox
  3. Each attachment is extracted — XML-first, then AI if needed
  4. A Sales Invoice is created with source channel Email
  5. Tapr tries to match the seller on the document to a Legal Entity
  6. Successful messages move to a success path; failures go to an error path
  7. Open Out Docs, review fields, set the PEPPOL receiver if needed, approve, and send
  1. From any mail client, send a message to the AR Username/Email shown in Tapr Settings
  2. Attach the sales invoice file
  3. Wait for the poll interval, or ask an admin to click Fetch AR emails now
  4. In Invoice Manager → Out Docs, open the new invoice and complete the send workflow

Connection failed: Verify password accuracy, confirm STARTTLS, and check mail server accessibility.

No invoices appear: Confirm AR Email is enabled, the message has an attachment, and fetch has run.

Extraction failed: Configure a BYOK AI key, try a cleaner PDF, or use a structured e-invoice (ZUGFeRD, Factur-X, UBL).

Wrong legal entity: Compare seller identifiers on the PDF with Legal Entity tax ID and PEPPOL registration.

Quota errors: Plan message limits — upgrade or wait for the next metering period.