Convert a Bank Statement to Import Into OneUp

Two ways to get transactions into OneUp

OneUp gives you two paths for bank data: connect the bank directly for an automatic feed, or import a statement file yourself. The manual path matters because feeds do not cover every bank, they can lag, and older history often falls outside the window a feed reaches. For the manual route OneUp accepts three file types, QIF, OFX, and CSV. If your bank hands you a QIF or OFX file, use it. When it does not, which is common for a PDF statement, CSV is the format you fall back to, and that is exactly what a converted statement produces.

Where to import: the Bank Activity view

The upload lives in OneUp's Bank Activity view. Open it, click the Import Bank Statement button, and choose your file. OneUp then shows a list of the bank account movements it read from the file so you can look them over before anything lands in the books. Because this is a review step, the cleaner the file you feed it, the less you have to correct on screen, which is where converting the PDF into tidy, column-separated rows pays off over retyping figures by hand.

OneUp's CSV formatting rules

OneUp is specific about how a CSV must look, and getting it wrong is the usual reason an import stalls. The file needs headers OneUp can read so it knows which column is the date, the description, and the amount. Dates have to be in mm/dd/yyyy form. Amounts must be plain numbers with the currency setting at NONE, so no dollar signs or currency symbols in the amount column. Converting the statement lets you produce a CSV that already follows these rules rather than hand-editing a raw export line by line.

Automatic Accounting matches your imports

Once the movements are in, OneUp tries to match each one against the sales invoices and purchases it already knows about, and it leans on the matches you made in the past to do it. That is the idea behind its Automatic Accounting: the more you confirm, the more it categorizes on its own next time. Before that happens you still choose which movements to import and can change them, so a clean converted file keeps the descriptions and amounts intact and gives the matching engine good text to learn from.

Accuracy and privacy

Because OneUp reads the file column by column and then tries to match it, an accurate CSV keeps both the import and the auto-matching honest, so every transaction is reviewable in the converter before export. The output arrives with dates and amounts already in the shape OneUp expects. Since a statement holds real account activity, the file is processed to build the CSV and then deleted automatically, with nothing kept on a server afterward.

Frequently Asked Questions