{"id":8892,"date":"2025-07-29T11:12:17","date_gmt":"2025-07-29T11:12:17","guid":{"rendered":"https:\/\/tugelapeople.com\/?p=8892"},"modified":"2026-02-10T14:47:06","modified_gmt":"2026-02-10T14:47:06","slug":"from-road-trips-to-apis","status":"publish","type":"post","link":"https:\/\/tugelapeople.com\/de\/blog\/from-road-trips-to-apis\/","title":{"rendered":"From Road Trips to APIs: Sage People Payroll"},"content":{"rendered":"

Who knew a day\u2019s training at Sage in Newcastle could be so exciting?<\/strong><\/h2>\n

When three members of the Tugela People team headed to Sage HQ in Newcastle, they didn\u2019t expect to return quite so energised by APIs, testing tools, and even a few unexpected \u2018consumer secrets\u2019.<\/p>\n

Louise<\/strong> Connah<\/strong><\/span><\/a> (our Payroll Bureau and Implementation Manager), Karen Gardener<\/strong> <\/span><\/a>(Senior HRIS Consultant), and Bella O’Brien<\/strong><\/span> (HRIS Apprentice) attended a focused, hands-on training session exploring the brand-new Sage People to Sage Payroll API integration, and returned with a wealth of insight, enthusiasm, and a clear sense of momentum.<\/p>\n

Between them, they brought a broad cross-section of experience from across Tugela People\u2019s services, including payroll management, HRIS implementation, and managed services. Their reflections made one thing very clear: this integration could be a real game-changer for our clients.<\/p>\n

\u201cIt\u2019s genuinely got me excited about doing payroll integrations again<\/em>,\u201d said Karen. \u201cAnd I don\u2019t say that lightly.<\/em>\u201d<\/p>\n

This new API integration is currently in the early adopter phase, and we\u2019re already working closely with a client to implement it ahead of the<\/span> general release<\/span>.<\/span> Once live, it will be available to both new and existing clients who use Sage People<\/a> alongside Sage People Payroll<\/a><\/strong>,<\/span> replacing the current Payflow integration method<\/span><\/strong>, which has been the go-to solution until now.<\/p>\n

Why it matters<\/strong><\/h2>\n

As the team explained, Payflow<\/strong><\/span>, the current integration method, relies heavily on CSV files, SFTP folders, and manual handling. It\u2019s functional, but fragile. Even minor formatting issues can throw the whole process off.<\/p>\n

\u201cPayflow doesn\u2019t always play nicely<\/em>,\u201d Louise explained. \u201cIt works, but there are a lot of blurred lines around what fields can be used. And as payroll professionals, we like clarity. And control!<\/em>\u201d<\/p>\n

The new API-based integration<\/strong><\/span> is designed to address those frustrations, enabling a secure, consistent, and automatic data flow<\/strong><\/span> from Sage People to Sage Payroll. Crucially, though, it\u2019s not a \u2018black box\u2019. It includes a holding area<\/strong><\/span>, providing payroll professionals with visibility and control before any information is committed to payroll.<\/p>\n

\u201cNo payroll person wants data being loaded straight into the system without their say-so,<\/em>\u201d Karen pointed out. \u201cThe holding area is exactly what people have been asking for.<\/em>\u201d<\/p>\n

Louise agreed: \u201cWe don\u2019t just want a salary change pushed in. We want to see it. Check it. Validate it. And then we decide when it goes in<\/em>.\u201d<\/p>\n

Why change is required<\/strong><\/h2>\n

While Payflow has long been the default for Sage People to Sage Payroll integration, it hasn\u2019t always been the most efficient or scalable option, particularly for growing clients with multiple payrolls and complex data requirements. It relies on multiple CSV files, SFTP folders, and a long list of fields that don\u2019t always align neatly between systems.<\/p>\n

\u201cIt works, but only because we\u2019ve learned how to make it work<\/em>,\u201d said Karen. \u201cThere are too many places where things can fall over, and it\u2019s different every time depending on the setup. The API gives us a standard, something we can rely on.<\/em>\u201d<\/p>\n

Even something as simple as opening a CSV file to check it can corrupt the formatting or remove leading zeros, which then leads to failed uploads and extra work. Louise explained, \u201cIf a client opens the file and it defaults to opening in Excel, it can completely mess up the formatting. We\u2019ve had issues where bank account numbers lose digits or salary fields convert to date formats. And when you\u2019re uploading to payroll, one small mistake can have a big impact<\/em>.\u201d<\/p>\n

That day-to-day complexity has driven the need for something more consistent, scalable, and robust. One that supports growth and flexibility, without starting from scratch each time.<\/p>\n

A big shout-out to the Sage People team<\/strong><\/h2>\n

It\u2019s worth recognising just how much collaboration has gone into building this new integration. The Sage People product and development teams<\/strong> <\/span>have clearly taken on board feedback from consultants, partners, and clients alike, building a tool that reflects the day-to-day realities of payroll operations.<\/p>\n

Their focus on usability<\/strong>, commitment to listening<\/strong>,<\/span> and drive to deliver something practical and scalable<\/strong><\/span> really stood out on the day and didn\u2019t go unnoticed by our team.<\/p>\n

What\u2019s in it for clients?<\/strong><\/h2>\n

Plenty. Once released, this new integration will offer:<\/h3>\n