§13b UStG Reverse Charge on Invoices from Indian Software Vendors
Invoices from Indian vendors carry no German VAT, but German VAT is still due. Who owes it, when it arises and what to check on every invoice.
Read →// 55 articles
Invoices from Indian vendors carry no German VAT, but German VAT is still due. Who owes it, when it arises and what to check on every invoice.
Read →Abnahme is the legal hinge of a Werkvertrag. In agile projects it only works if the contract defines what, when and against which criteria.
Read →Reclassification is not a single penalty but a chain of civil, administrative and social security consequences. A CTO-level walk-through.
Read →Dedicated developer offers are often drafted for markets without an AÜG. Twelve clauses German buyers should read twice before signing.
Read →Remote access from India to systems with personal data is a third-country transfer. The document set is manageable if you build it in the right order.
Read →An EOR hires people you manage, a managed pod delivers work the vendor manages. The legal allocation of risk differs more than the price.
Read →German law does not transfer copyright, Indian law limits silent assignments. A rights chain that works in both systems has to be written explicitly.
Read →German social security law is territorial, but that does not make individual offshore freelancers risk-free. A sober map of what remains.
Read →The status determination procedure is the only way to obtain a binding answer on freelancer status in Germany. Here is how to use it deliberately.
Read →Most AÜG risk is created in Jira and in the daily stand-up, not in the contract. A practical guide to where the line runs.
Read →Three legal models, one practical question: who directs the engineers, and can your organisation keep it that way for two years.
Read →With a time offset of 3.5 to 4.5 hours, review latency becomes the hidden bottleneck. A layered gate design keeps quality high without stalling delivery.
Read →Most friction between German clients and remote teams is not technical. It comes from different defaults on directness, documentation and commitment. Here is how to align them.
Read →The best time to plan an exit is before signing. A transition clause and a handover runbook turn a potential crisis into a scheduled project.
Read →A 3.5 to 4.5 hour offset can extend your coverage or create gaps. A clear model for severity, roles, access and reporting decides which.
Read →Lock-in is rarely written into a contract. It accumulates in accounts, undocumented decisions and single points of knowledge. Here is how to prevent it from day one.
Read →A Leistungsbeschreibung that lists activities instead of results protects nobody. Here is a structure that engineers and lawyers can both work with.
Read →Hours logged say little about delivery. Team-level DORA and flow metrics show whether an external team creates value, without turning you into its line manager.
Read →Remote engagements rarely fail in week one. They fail in weeks three to six. A structured 30-day plan makes the ramp measurable.
Read →A second pod does not double output by default. It adds a coordination problem. Here is how to decide whether to scale and how to split the work so that it pays off.
Read →Before a remote team touches your code, a few controls must be non-negotiable. A baseline that maps to ISO 27001 and TISAX expectations without inventing a new framework.
Read →Agile sprints and German contract law can coexist. The key is turning the sprint review into a documented acceptance step with clear defect classes and deadlines.
Read →Three ways to staff a new product line, a scoring matrix to choose between them, and a phase plan that avoids locking in too early.
Read →Hourly, monthly and fixed-fee quotes cannot be compared directly. A worksheet that converts them into one number you can defend.
Read →An unfilled engineering role shows up as a budget saving. Three calculation methods that reveal what it actually costs.
Read →Headcount plans overstate delivered capacity. A method to budget engineering in engineer-months, with hiring lag and ramp-up built in.
Read →Each pricing model allocates risk differently and interacts with German contract law in its own way. A decision framework for buyers.
Read →Four ways to add engineering capacity, compared on the cost lines that matter and the legal risk each one carries in Germany.
Read →The rate is negotiated. The cost is in the clauses. Twelve contract provisions DACH buyers should read before signing an offshore deal.
Read →CFOs approve business cases, not rate cards. A structure for presenting external engineering capacity in the language of finance.
Read →Gross salary is only the starting point. A line-by-line method for the full cost of a senior engineering hire in Germany in 2026.
Read →A structured checklist for procurement and engineering leads to assess an offshore engineering vendor before the first contract is signed.
Read →An honest list of situations in which offshore engineering will cost more than it saves, and the alternatives that fit better.
Read →Works councils rarely block external engineering capacity on principle. They block surprises. Plan the conversation accordingly.
Read →English works for code. Lastenheft, Abnahme and the Werkleiter's concerns are negotiated in German.
Read →The headline shortage has shrunk, but for a scaleup with a funded roadmap the hiring math has barely changed.
Read →Indian city profiles differ more than most DACH buyers realise. Match the hub to the workload, not to the brochure.
Read →Offshore engineering is not a red flag in due diligence. Undocumented offshore engineering is.
Read →Some concerns about offshore engineering are justified, some are outdated, and a few point at the wrong cause entirely.
Read →Nearshore and India solve different problems. The right choice depends on which constraint actually binds your roadmap.
Read →Most offshore engagements that fail could have been predicted from the answers to a few questions nobody asked.
Read →Five developments will shape how DACH companies source engineering capacity in 2027. Most of them are already dated and documented.
Read →Three external engineering models, three different allocations of control and risk. Choose by who should steer the work.
Read →The same offshore contract can be sound in Munich, questionable in Vienna and prohibited in Zurich. Know the differences.
Read →A remote team does not lower your ASPICE level, a missing process interface does. How to integrate external engineers into an automotive software process.
Read →Sending code to a remote team can be an export. A traffic-light framework for defense and dual-use companies considering offshore engineering.
Read →Outsourcing model development does not outsource the provider role. How to allocate AI Act evidence across an external team.
Read →The manufacturer stays responsible under MDR. How to allocate IEC 62304 activities and evidence when an external team writes the code.
Read →The eight practices of IEC 62443-4-1 translated into concrete requirements and evidence for an external development team.
Read →An offshore software team is a supplier in your QMS. Classification, quality agreement clauses and monitoring that will hold up in an audit.
Read →From January 2027, software is explicitly a safety component. A framework for deciding which robot software work can sit with a remote team.
Read →Remote access is a transfer. Four architecture patterns that keep training data in the EU while a remote team runs the ML platform.
Read →Shop floor integration is mostly interface work. How to use OPC UA information models and simulated endpoints so a remote team can deliver.
Read →Robots are physical, most robot software is not. How to split a ROS 2 stack between a remote team and your lab without losing velocity.
Read →Clean core becomes enforceable when it is an acceptance criterion. How to scope S/4HANA extensions for a remote team using SAP's A to D levels.
Read →