- 01What Dropbox data does Well pull into Pennylane?
- Well watches Dropbox for attachments matching the configured invoice and receipt filters, extracts supplier-invoice and document files read from a watched folder via Apideck file-storage, and forwards the structured output to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the original email message ID stored on every record for audit.
- 02Will every Dropbox record post to Pennylane automatically?
- Not always. At the next fifteen-minute polling window, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Pennylane email-in address and Pennylane drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
- 03Does Well handle multi-currency records between Dropbox and Pennylane?
- Dropbox carries the original transaction currency on every record and Pennylane natively ledgers in multiple currencies. Well preserves the original amount, applies your Pennylane chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Pennylane, so the Pennylane entry you post keeps both sides of the trade.
- 04How does Well prevent duplicates when posting Dropbox records to Pennylane?
- Every Dropbox message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Pennylane entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Pennylane.
- 05What happens if a Dropbox record fails to post to Pennylane?
- When a record fails to post to Pennylane (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Dropbox record. Nothing silently drops.
- 06How does Well authenticate with Dropbox and Pennylane?
- Dropbox runs a manual OAuth 2.0 flow that you approve inside Dropbox; Well receives a refresh token scoped to the resources it needs to read. For the delivery side, Well forwards the reconciled document to your Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Dropbox hosts outside the EU; Well processes records per the storage region configured for your workspace.