Portal Hound

Portal Hound for finance back office

Vendor, bank and payroll portals for your offshore finance team, with a name on every session.

Invoice portals, bank platforms, expense tools and payroll systems move money. Portal Hound gives your offshore finance staff named access to the ones you approve, from one company-owned U.S. address, with a log your controller and auditors can rely on.

The problem

Money moves through portals, and auditors want a name on every move.

Bank platforms and payment portals are the strictest systems about where logins come from, and the first your auditors ask about. Shared logins for an offshore AP team fail segregation-of-duties, and a wire released under a shared login has no accountable person.

Bank platforms lock on foreign logins

Treasury and bank portals challenge or block logins from abroad, often by contract.

Segregation of duties

If three people share the login that approves payments, you have no segregation of duties, and your auditor will say so.

Vendor portal sprawl

Dozens of customer and vendor invoice portals, each with its own login, each shared by habit.

How it works

One button for workers. Full control for you.

You approve the portals

Add each platform your team works in. Portal Hound suggests the domains it needs, and nothing is reachable until you approve it.

Workers press Connect

They install a small app for Windows or Mac, sign in with their work email, and connect. There's nothing to configure.

Only approved portals go through

Those platforms are reached through your company's U.S. gateway, tied to that person and logged. Email, banking and everything else use the worker's own connection.

Platforms

The portals these teams approve first.

Any web platform can be approved. These are typical for finance back office (ap, ar, payroll).

NetSuite, Sage Intacct, DynamicsBank and treasury platformsBill.com, Tipalti, CoupaVendor and customer invoice portals (Ariba, Tungsten)Expense tools (Expensify, Ramp, Brex)ADP, Paychex, RipplingCollections and lockbox portalsTax and filing platforms

What you get

Named users, one company address, an access log for the audit file.

  • Every AP, AR and payroll specialist has their own user on each platform; Portal Hound never shares a login.
  • All finance-portal logins come from your company's one U.S. address.
  • Access logs tie every session to a person, which supports segregation of duties and the audit file.
  • Revoke a departing employee in one click, without touching the bank platform's other users.
Portal Hound admin console

Requirements

Portal Hound is for teams already allowed to work offshore.

It controls and records how your team reaches portals. It doesn't change who is allowed to use them, or where from.

Your agreements must permit offshore access

Bank platforms, payment processors and tax agencies frequently prohibit access from outside the U.S. or require named users and disclosure. Check each platform's terms and your banking agreements before routing it. Portal Hound is not a way around a portal's location rules.

Every person uses their own login

Your team members sign in to each platform with accounts issued to them, in the role they need. Portal Hound never shares, stores or fills in a login, and it isn't for working as somebody else.

Regulated data stays your responsibility

Payroll and banking data are sensitive personal and financial data under several laws. Your controls, approvals and training still apply.

Tell your team access is logged

The access log records which person reached which platform and when. Tell them, and follow the privacy and employment rules where they work.

Portal Hound doesn't guarantee access to any portal. The companies that run them decide who may use their systems. Full requirements.

Questions from finance back office (ap, ar, payroll)

Will our bank allow this?

Only your banking agreement can answer that. Many banks restrict portal access to the U.S. and to named users with hardware tokens. Where the bank permits offshore users, Portal Hound gives them one address and a log; where it doesn't, keep banking onshore.

Does it help with SOX controls?

It supports the access-control and logging parts: named users, a controlled access path and a record of who reached which system. Your approval workflows and reviews remain your controls.

Can approvers be onshore and preparers offshore?

Yes. That's a common split: offshore staff prepare in the ERP and vendor portals through Portal Hound, onshore staff approve and release payments.

See Portal Hound with your own portals.

We'll show you the worker app and admin console, and talk through setting up a gateway for your team.