How to use ERPIGEON

Tap, review,
save, and move on.

The app handles validation behind the interface. You create a draft, review proposals, correct visible issues, and save.

01

Get started

  1. Open the app and choose Personal or Business.
  2. Select Korean, Japanese, English, or Simplified Chinese in Settings.
  3. Use Personal immediately for receipts and private settlement.
  4. Use Business Core for business documents and FlowTwin after Business Core for procurement processes.
  5. If app lock is enabled, verify Face ID and the device passcode first.
You do not need to configure everything first.Create a draft or order, then add fields as the work requires them.

02

Personal receipts and settlement

  1. Use receipt capture, single-page scan, or photo selection.
  2. Review merchant, date, total, tax, and item rows.
  3. Do not confirm when the total and item sum disagree or an item amount is implausible; tap and correct the row.
  4. Verify color or A/B marks, then connect them to people. A color can be confirmed before a person is assigned.
  5. Complete settlement and review it again in Records and Ledger.
Recognition is a proposal.Warnings and reconciliation failures help focus review, but the user makes the final confirmation.

03

Business documents and transactions

  1. Review issuer details, document numbering, currency, and amount or quantity precision in Business Settings.
  2. Register counterparties and catalog items manually or preview a standard import file.
  3. Draft and save a quote before navigating to a transaction that requires an approved quote.
  4. Keep quote and PO references while creating proforma and commercial invoices.
  5. Track payment terms, remittance evidence, receivables, and closing status.

Issued or approved records are not silently overwritten. Use correction, cancellation, or replacement-document flows.

04

FlowTwin orders and processes

  1. Start a new process with only an order number and target delivery date.
  2. Add producer, distributor, forwarder, customer, product, and transport information when it becomes available.
  3. Compare the plan marker with actual progress. The plan follows the calendar; actual progress moves only after evidence-backed completion.
  4. Review today's high-risk work and predecessor relationships first.
  5. Use a schedule revision for planning changes and a completion record for actual execution.
Schedule approval is not completion.Save the actual completion date and an attachment or reference before the blue current-step marker advances.

05

Excel, CSV, and JSON collaboration

  1. Save or share the blank standard Excel template from FlowTwin.
  2. On Mac or PC, edit the input sheet; do not overwrite locked history or raw-data sheets.
  3. Select the file in the app and review orders, steps, predecessors, progress, and errors.
  4. Confirm order IDs and revision context, then approve the batch.
  5. When exporting app changes, append history instead of deleting previous rows.

The app-provided template is recommended. An arbitrary workbook is offered only as a preview candidate when its headers and business IDs can be identified.

06

Save, complete, correct, and remove

  • Draft: edit, autosave, cancel, or discard.
  • Registered order: archive and restore; linked records are not silently deleted.
  • Process completion: requires an actual date and evidence or reference.
  • Issued record: use correction, cancellation, or replacement history.
  • Shipment and inventory: enter a reason and use an adjustment or reversing movement.

If save fails, keep the screen open, confirm that input remains, and retry.

07

Purchase and restore

  1. Review the localized price and description on Apple's purchase sheet.
  2. Business Core is required before FlowTwin Procurement.
  3. Use Restore Purchases to recheck verified purchases for the same Apple Account.
  4. Pending, cancelled, or unverified purchases may block new paid editing while preserving access and export for existing records.

Apple handles billing and refunds through purchase history or reportaproblem.apple.com.

08

CloudKit and multiple devices

Where released and enabled, synchronization uses the user's Apple CloudKit private database. A local save and arrival on another device are separate states.

  • Do not create a duplicate order while a transfer or conflict is pending.
  • Check network and Apple Account status, then retry from sync status.
  • Merge Mac or PC workbook changes through revision preview.
  • Concurrent company staff work in L’addition Cloud is a separate product, not a current local-edition feature.

09

Troubleshooting

  • Record the visible error and affected screen.
  • Note app version, build, device category, OS, and reproduction steps.
  • Use only screenshots with personal information redacted.
  • Do not send original receipts, account or card details, passwords, counterparty emails, or confidential documents.
Open supportPrivacy policy