Your daily payment
review, explained.

Start with your next order

1. Sign in using your ChatGPT account. Use the same account whenever you return.
2. Create a named batch, such as “October 12 orders”. Add orders one at a time or download the orders CSV template and replace its example row.
3. Download your receiving account’s transactions from your bank or wallet. Map the columns to the bank CSV template. Keep the full transaction reference and timestamp; use CREDIT for incoming money and DEBIT for outgoing money.
4. Use the same account label in both files, such as bank-main. Give each separate receiving account a distinct label, and reuse that label consistently across batches. Only confirm reference correspondence when you have checked that the receipt and receiving statement use the same reference scheme.
5. Enter the statement’s full coverage period, including its timezone. Upload the bank CSV. Tick full coverage only if the statement contains every transaction in that period.
6. Attach a JPG, PNG or WebP receipt to its order. Check its amount, full reference, timestamp and status against the original image, then save.
7. Click Compare evidence. Inspect the reasons, resolve missing evidence and compare again. Export the results CSV or download the complete batch records as JSON.

Receipt timestamps without an offset are interpreted as Pakistan time. A complete example is 2026-10-12T14:22:00+05:00. Orders and bank statements can also be imported from PDF: choose Upload PDF, enter your Gemini key and consent, then check the extracted table against the original before importing. You can correct fields before saving. Missing timestamps must be obtained from the original account records, never invented. Receipt uploads still accept images only.

Read the result before acting

SHIP

The supplied evidence meets the matching rules. Confirm the payment in your actual receiving account before releasing goods.

HOLD

The supplied records do not show the required matching payment. Check the reason and request corrected or missing evidence.

REVIEW

Details are incomplete, ambiguous or conflicting. Resolve them before making a shipping decision.

Milaan does not connect directly to your bank, move money, certify settlement, or reliably detect every edited receipt. Matching uses uploaded records; an inaccurate statement can produce an inaccurate result. Reusing a bank credit across saved batches is checked within the same user account. Separate users do not share an allocation ledger.

Optional receipt reading

You can use Milaan entirely with manual receipt confirmation. Gemini can prefill visible fields if you enter your own Gemini API key and agree to send that receipt to Google. The key stays in the current tab’s memory and is sent through the Milaan server for that request; the application does not save it. Your Google account’s quota and charges apply. Always inspect extracted fields before confirming them.

Your records and privacy

Authentication uses ChatGPT. PDF extraction sends the selected document to Google with your consent. The application does not retain the original PDF; keep your copy. Only the table you confirm is saved. Your API key is not saved. The application stores your account identifier with your batches, orders, bank transaction details, receipt images and saved results. Records and images are stored in hosted Cloudflare database and object storage. Application access is restricted to the account that uploaded them; public visitors cannot browse them.

Upload only records you are entitled to process. Crop unrelated personal details out of receipt images and remove unrelated bank CSV columns before uploading. Never upload bank passwords, PINs, OTPs or card security codes. Milaan does not need them.

Records remain saved until you delete the batch. The batch delete action removes its application records, receipt images and credit allocations. It cannot erase exports you previously downloaded or any receipt already sent to Google. Cloud-provider operational logs and backups follow their own retention policies; this application does not promise immediate erasure from those systems.

The Records download includes order and bank data, receipt fields, decisions and the last 150 activity entries. Original receipt images are separate: open a receipt and use Download image. Keep your original bank statements and receipts independently. The export is a record for your own use, not an automatic restore file.

Current service limits

25 saved batches per user; up to 200 orders, 2,000 bank entries and 100 receipts per batch. CSV uploads are limited to 2 MB and receipt images to 5 MB each. PDF extraction accepts files up to 5 MB and 200 records; larger or encrypted documents may need splitting or a CSV export. This release is a single-user workspace; shared team accounts, direct store integrations, bank connections, guaranteed uptime and automatic backup restoration are not included.

Changing evidence clears the displayed results. Run Compare evidence again. Credits already allocated remain reserved until you successfully compare the edited batch again or delete it. If another tab changes a batch, reload before continuing.

Need help?

Contact bil332204@gmail.com with the error message and steps that led to it. Do not email financial records or API keys. Milaan began at AiCON ’26 and is now maintained as an online reconciliation product.