KeyPay.

It only ever reads

Nothing is written back to your system. Changing something elsewhere is what Action MCPs do, and they are a separate, deliberate choice.

It refreshes overnight

With a midday refresh on higher plans, and an on-demand refresh whenever you want one.

It lands rows, not summaries

The underlying records, which is what makes a figure joinable to a different system later.

It is maintained

Written against a specific API that will change without warning. When a vendor ships a breaking change, that is our problem.

One system answers questions about itself.

Two answer questions neither can. KeyPay next to your ledger is where the interesting questions start, because one of them says what happened and the other says why.

Does VibeCFO integrate with KeyPay?

Yes. KeyPay connects to VibeCFO and its data lands in your own database, where it can be reported on, trended and joined to your other systems.

What can I do with KeyPay data in VibeCFO?

Ask questions of it in plain English, build reports that combine it with your accounting ledger and other operational systems, and put a Pulse on any figure so you are told when it moves.

Can I join KeyPay to my accounting system?

Yes, and that is usually the reason people connect it. Two systems in one warehouse answer questions neither could answer alone - your ledger says what happened, the operational system says why.

Where does my KeyPay data go?

Into a database in your own region that belongs to you, not a shared tenancy. It is never used to train any model, ours or anyone else's, and it is removed entirely if you leave.