Collect Marker.io invoices by workspace, team seats, project, widget, billing period, currency, tax, credit, and plan change so visual bug-reporting costs stay allocatable.
Match Marker.io bills to the workspace that collected the feedback. Marker.io bills the website-feedback and visual bug-reporting product, not the underlying hosting or issue tracker. One customer can hold several workspaces, seat packs, or project widgets. Keep workspace and project identifiers with each invoice so design, QA, and client sites are not collapsed into one software total.
Automatic download of Marker.io invoices
The planned flow joins portal documents with mailbox attachments in one review list. Until this provider connection is released, use the following checklist as the reliable manual path.
How it works
- Set the account and period. Identify the billed Marker.io workspace and owner before collecting invoices from several client sites.
- Check the original documents. Compare seats, projects, widget or plan name, service period, currency, and tax with the active subscription.
- Prepare the handoff. Keep upgrades, seat changes, and credits linked to the billing period they actually change.
Ready to save time?
BillGetter brings portal documents and email attachments into one review flow — locally or in the cloud.
- Connect the Chrome extension
- Retrieve only new invoices
- Directly in Chrome
Illustration of the BillGetter interface with invented document data.
Frequently asked questions
How does BillGetter protect my Marker.io data?
BillGetter is being developed as a local and a cloud version. The permissions and data path of the Marker.io connection will be shown before you connect an account; the integration is currently on the roadmap.
Can I collect older Marker.io documents?
The available history depends on the later Marker.io connection and the documents retained in the account. BillGetter will document that scope before the integration is released.
Does BillGetter also collect invoices from email?
Mailbox collection is part of the planned BillGetter workflow. Email attachments and portal documents are intended to appear in the same review list, with the exact early-access scope confirmed before release.
Which Marker.io documents belong in the monthly set?
For Marker.io, start with: Workspace subscription invoice, Seat or project adjustment, Credit or plan-change document. Keep corrections and credits with the same period so the set remains complete and understandable.
Are Marker.io documents always saved as PDFs?
BillGetter is intended to retain the original format supplied by Marker.io; not every document type is necessarily a PDF. Before export, use this rule: Preserve the original Marker.io invoice number and add workspace or project allocation as separate internal context.