Export your payments

What to pull from your billing system, and what has to be in it.

If your billing system is not Stripe, or you would rather not connect it, export your payment history as a file. Most systems call it a payments report, a transaction export or billing history. You want one row per payment, not a monthly summary.

What the file needs

Who paid	A customer ID, name or email. Anything that identifies a customer consistently from month to month.
How much	The amount of the payment.
When	The date the payment was taken.

Everything else helps. A plan name, a plan length, a segment, an account owner or a payment status all become ways to break the month down, and a plan length lets Morevy spread prepaid plans across the months they cover.

Limits

.csv or .xlsx. Older .xls files need to be saved as one of those first.
Up to 25MB and 60,000 rows per file. A larger file is refused with the number of rows it has. Export a shorter date range instead, or split the history into more than one file.
One currency per file. A file that mixes currencies is refused until it is converted or split by currency. Morevy can only detect mixed currencies when the file has a currency column; without one, every amount is treated as the same currency.

How much history to include

Include at least the month you want to review and the month before it, since every movement is measured against the previous month. A year or more gives Morevy enough history to show returning customers, trends and cohorts. Stay within the 60,000-row limit.

Uploading

Start a New workflow and drop the file into Drop CSV or Excel files here. Morevy reads it on the spot and shows you how it read it before anything is calculated. The file is not sent to the AI model; for what the model does see, and how customer names are protected, see Data handling and privacy.

If the date range Morevy reports is shorter than you expected, the export was probably filtered. Many systems default to the last 30 or 90 days.