Pellovan
Get helpBack to website
Prelaunch · fictional data onlyCalculated on this device

Two files. A clear comparison.

Try a payment register against a bank export. Confirm columns, run the rules, then review the exceptions.

Real customer files and purchases remain unavailable. This working demo uses fictional transactions only. No file chooser, accounts or saved financial records.

01 / Files and columns

Start with the sample files

Payment file

Fictional payment register

Load the sample files to preview and confirm columns.

Bank file

Fictional bank export

Load the sample files to preview and confirm columns.

Check the column preview

Date and amount must use different columns. References should be original text, not Excel-converted numbers.

Read troubleshooting guidance

02 / Matching rules

Confirm how to compare

Reverse signs only when the bank uses the opposite convention for both payments and refunds. Separate debit/credit columns are unsupported.

Confirmed pairs need a unique reference, exact signed amount and dates within the window. Amount-only candidates always require review.

Fictional files establish USD and the selected date order. Exact identifiers preserve case, spaces and Unicode; differences require review.

Check interpretation before running

Confirm currency, dates, decimals and signs from the source. Do not adjust rules merely to make unresolved records match.

Read troubleshooting guidance
Check larger fictional datasets on this device

This development check generates unique references with known exact matches. It is not a customer performance guarantee.

Help / Self-service first

Get help with your run

Email human support

Use these guides for routine questions, or email directly. No chatbot is required. Pellovan’s founder is the designated human contact. Email delivery and replies passed testing; founder inbox access and coverage still need verification.

Prepare files and confirm columns

This workspace accepts fictional samples only. The parser supports CSV and one visible, flat XLSX worksheet. Customer files remain disabled.

  1. Use one header row with distinct column names. Avoid merged cells, hidden rows, formulas and external links.
  2. Map date and amount to different columns. A reference helps establish exact matches; preserve identifiers as text.
  3. Check the preview against your source. Do not change source values simply to obtain a match.
Resolve dates, currency and amount signs

The fictional samples establish USD. The selected date and decimal conventions apply to both files; separate per-source conventions are not available.

  1. Do not guess whether 03/04 means March 4 or April 3. Verify the source convention or export ISO dates.
  2. Choose the decimal convention used by the source. Amounts are not rounded to force a match; other currencies are unsupported.
  3. Reverse bank signs only if the bank uses the opposite convention for both payments and refunds. Separate debit/credit columns are unsupported.
Understand confirmed and unresolved results

Confirmed pairs meet the selected exact rule. They are not an audit or proof a payment cleared. Everything else requires review.

  1. Possible matches are proposals, not verified matches. Compare original references, dates and signed amounts.
  2. A discrepancy can have several explanations. Compare source records before deciding whether fees, partial payments or reversals apply.
  3. Duplicate candidates and unmatched records do not establish duplicate payments, failures or outstanding balances. Split and aggregated matching are unsupported.
Recover from mapping and processing errors

An error does not authorize guessing. Keep the original files unchanged and review the stated reason.

  1. For mapping errors, select distinct valid date and amount columns, check the preview, then run again.
  2. For unsafe identifiers, obtain a fresh text export from the source system. Excel-rounded identifiers cannot be reconstructed.
  3. If processing stalls, cancel and retry with fewer open tabs. Refresh clears this run. Real low-memory behavior is not yet verified.
Download reports and protect your data

The exception CSV includes unresolved findings. The Excel report includes Summary, Exceptions and Confirmed sheets with source-row references.

  1. Report preparation runs in a local worker. Canceling stops processing; rerun or request the report again when ready.
  2. Financial records remain in browser memory. Refresh clears the run, but does not delete reports already downloaded to your device.
  3. Email is separate from local processing. Never send financial files, bank details or unredacted screenshots to support.

Contact a human without sharing financial records

Email leaves your device. Do not attach files, reports, bank details or unredacted screenshots. No response time is guaranteed.

Open a support email

Opens your email app with a blank, topic-based template. Nothing is sent automatically or copied from your run.

Suspect an incorrect result? Stop relying on the affected result and contact support with non-sensitive steps to reproduce it.

If your email app does not open, write to rowmark@nanocorp.app.