Get Ubeo Open Invoices

UBEO's own open invoices -- past-due and current together, oldest due date first. Frederick, 2026-09-24: "Frederick wants to see UBEO's OPEN invoices, both past-due and current: invoice number, date, due date, amount, and whether a later email shows it paid."

Read from email -- see app/modules/finance/ubeo_invoices.py. paid_status_words is the honest word for what the email trail can and cannot show: "Open, unpaid" when confirmed still owed, "Paid status unknown from email" when only ever named in a past-due reminder with no Payment Receipt since -- never a guessed "paid".

⛔APPENDED 2026-09-24: Frederick sent UBEO's own PORTAL screenshots the same day -- 11 open invoices, $14,610.89, all unpaid in full -- against this reader's 4, $12,104.88. The gap: 7 invoices whose email Payment Receipt showed a $0.00 remaining balance for a check payment that (by every sign available in the mailbox -- no reversal or bounce email exists anywhere) did not, in fact, clear -- something this reader has no way to see from email alone. Frederick's ruling: the PORTAL, read by Rooster's own browser (app/modules/finance/ubeo_portal.py), is the PRIMARY source now; this email reader is the FALLBACK.

⛔APPENDED AGAIN, SAME DAY: this route now reads ubeo_invoices. ubeo_summary, not a hand-rolled total -- ubeo_invoices is the SAME table both readers write into (by the same normalized invoice number), so the response is automatically portal-sourced once a portal read has ever landed a row, and email-sourced (as before) for anything the portal has not yet confirmed. summary_words is UbeoSummary's own ("UBEO: $X outstanding, $Y past due, next due <date>", Frederick's own wording), never the older "Email shows..." line, which read as understating a figure the table may already have corrected.

⛔THE SAME GRANT AS THE OTHER COMPANY-NUMBERS ROUTES. Writes nothing.